Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Upgrade instructions from 3.x to 4.x #1142

Open
pwonson opened this issue Dec 13, 2022 · 1 comment
Open

Upgrade instructions from 3.x to 4.x #1142

pwonson opened this issue Dec 13, 2022 · 1 comment

Comments

@pwonson
Copy link

pwonson commented Dec 13, 2022

Describe the bug
Any patches or releases that include database or other changes that need to be applied should be identified and the path to upgrade documented from the previous major version.

Before you install version 4.x.x, first you need to move from 3.4.0 to 3.4.10

3.3.18 -> 3.4.0 -> 3.4.10 -> 4.x.x

Source page
Upgrading

@pwonson
Copy link
Author

pwonson commented Dec 13, 2022

Detailed instructions:

Thanks for your patience, in order to achieve the upgrade from 3.3.16 to 4.x.x, please follow these steps.

1-backups folders
/etc/rundeck/libext folder
/etc/rundeck/rundeck-config.properties

2-backup your database

3-Start from 3.3.16
3-1) Then upgrade to 3.3.18, and check everything is working fine
3-2) Now you are in 3.3.18 so In order to upgrade to Rundeck 3.4.0, The following steps should be performed in order:
Backup the rundeck database
Add the following two properties in the rundeck-config.properties file:
dataSource.dbCreate=update
grails.plugin.databasemigration.updateOnStart=false
Start Rundeck 3.4.0
Once Rundeck is fully started, Shutdown Rundeck 3.4.0
Change added dataSource.dbCreate from update to none in rundeck-config.properties.
Change the grails.plugin.databasemigration.updateOnStart setting to =true.
Restart Rundeck 3.4.0. Once initialization is complete, Rundeck is ready for use
4-Once all steps were completed, please proceed to install version 4.x.x

If you have more questions/doubts, please let us know.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant