Upgrade to 3.4.0 Causes Rundeck Application Not to Start Completely

[Russ Robinson]

After upgrading from 3.3.12.20210521-1 to 3.4.0.20210614-1, we are finding the Rundeck server will not start.  Since our initial Rundeck installation (and thereby our MySQL database's objects creation for Rundeck) started with

3.3.7.20201208-1; no additional database migration steps were needed per "Upgrading to Rundeck 3.4" doc.

See the attached service.log output file.  Any suggestions?

[Russ Robinson]

I just tried dropping the rundeckdb inside of MySQL and restarting Rundeck 3.4.0.  Still have this problem.

[rac...@rundeck.com]

Hi Russ,

Did you add this on your rundeck-config properties file to moving forward to 3.4.0?

Regards!

[Russ Robinson]

Yes - still no change.

[Felipe Gutierrez]

Hello

What kind of installation you have (rpm / deb / war) what os? 

How did you performed the upgrade?

Regards

Felipe 

--
You received this message because you are subscribed to the Google Groups "rundeck-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rundeck-discu...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/rundeck-discuss/a1230f42-08da-4871-8a34-0afaa3b6ae3fn%40googlegroups.com.

[Russ Robinson]

RPM based on Oracle Linux 7.  Since we were on later 3.3.12 version, I just did yum upgrade on the rpm.

Thanks,

Russ

On Jul 22, 2021, at 12:37 PM, Felipe Gutierrez <fgutierr...@gmail.com> wrote:



You received this message because you are subscribed to a topic in the Google Groups "rundeck-discuss" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/rundeck-discuss/UXmlNHIfFu0/unsubscribe.
To unsubscribe from this group and all its topics, send an email to rundeck-discu...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/rundeck-discuss/CALWPzq-Sfgx-iFN1RG5k54hEtjeR6MZX-e3i0W1N-aGaov0FaQ%40mail.gmail.com.

[rac...@rundeck.com]

Hi Russ,

Did you follow these steps to perform the DB migration? (my first question looks like just adding a few parameters on the rundeck-config.properties but following these steps are needed).

Greetings.

[Russ Robinson]

Since I’m upgrading from 3.3.12, I just added/updated the following values into the config per the doc:

dataSource.dbCreate =none 

grails.plugin.databasemigration.updateOnStart = true

Thanks,

Russ

On Jul 22, 2021, at 1:21 PM, rac...@rundeck.com <rac...@rundeck.com> wrote:

Hi Russ,

To view this discussion on the web visit https://groups.google.com/d/msgid/rundeck-discuss/4acca0ee-8ddd-4de3-b754-da685a375b8fn%40googlegroups.com.

[Russ Robinson]

Even though I upgraded from just 3.3.12 - if I add the following lines into rundeck-config.groovy:

dataSource.dbCreate="update"
grails.plugin.databasemigration.updateOnStart="false"

All comes up fine with Rundeck 3.4.0 release.  However if I follow the instructions and remove those two lines (after the successful upgrade/start) and restart Rundeck, I get the errors and Rundeck fails to start.  If I set them to:

dataSource.dbCreate="none"
grails.plugin.databasemigration.updateOnStart="true"

I encounter the same Rundeck startup failure.

[rac...@rundeck.com]

Hi Russ,

Right, for 3.3.5 and above the "new lines" steps isn't needed, I tested upgrading a 3.3.13+MySQL (with some projects, executions, and keys) to 3.4.1 and the db migration works well. Please file a new issue here to follow up.

Thank you.

[Russ Robinson]

Out of curiousity, what version of MySQL were you using?

I found my issue.  It is related to the older version of liquibase being used and changed made in the newer version of MySQL Java Connector (8.0.23 and higher).  For now, I had to revert my connector version to 8.0.21 (as I did not have 8.0.22 on-hand).  From the liquibase tickets; it looks like they are telling interested parties that they need to upgrade to 4.3.1 or higher as there will be no new 3.10.x branches deployed (and thereby no 3.x.x versions with the fix).  I'm hopeful that Rundeck can be updated to the newer version of liquibase 4.3.1+ in a subsequent release.  I did detail my findings and fix here: https://github.com/rundeck/rundeck/issues/7184

[rac...@rundeck.com]

Hi Russ,

First test against MySQL 5.6.51 and the second test with MySQL 8.0.26.

1. Start a 3.3.13 instance against MySQL 5.6 (using the default MariaDB driver) or MySQL 8.0.26 (with 8.0.23 Java Connector).
2. Create some projects, scheduled jobs (to generate executions), and keys.
3. Wait to generate executions.
4. Stop the Rundeck 3.3.13 instance.
5. Start the Rundeck 3.4.1 (remember that the "add migraton lines" steps is to upgrade from Rundeck < 3.3.5, in this case (from Rundeck 3.3.12/3.3.13) just launching the 3.4 instance should works)

Regards.

[rac...@rundeck.com]

Reproduced here Russ, good catch. My last test with MySQL 8 was using 8.0.22 java connector, not 8.0.23 :-)