Fixes #16745: when upgrding rudder from 5.0 to 6.0, the rudder-pkg restaure pkg cannot restart correctly Jetty, so rudder-upgrade doesn't checkk compatibility, and rudder cannot start #2202
Conversation
| # Restore the plugins and checking them | ||
| if [ -f /tmp/rudder-plugins-upgrade ] | ||
| then | ||
| /opt/rudder/bin/rudder-pkg plugin restore-status < /tmp/rudder-plugins-upgrade |
There was a problem hiding this comment.
can you replace '/opt/rudder/bin/rudder-pkg' by calls to 'rudder package' command please ?
| @@ -168,6 +162,13 @@ echo "Done" | |||
| # Adjust permissions on /var/rudder/configuration-repository | |||
| /opt/rudder/bin/rudder-fix-repository-permissions >> ${LOG_FILE} | |||
|
|
|||
| # Restore the plugins and checking them | |||
There was a problem hiding this comment.
I dont get this. Currently we restore the status, then rudder-upgrade runs check-compatibility and rudder-postupgrade. Why doing it again just after?
There was a problem hiding this comment.
parent ticket change the order, but it wasn't such a great idea
|
PR updated with a new commit |
|
This PR is not mergeable to upper versions. |
|
OK, squash merging this PR |
…staure pkg cannot restart correctly Jetty, so rudder-upgrade doesn't checkk compatibility, and rudder cannot start
ncharles
force-pushed
the
bug_16745/when_upgrding_rudder_from_5_0_to_6_0_the_rudder_pkg_restaure_pkg_cannot_restart_correctly_jetty_so_rudder_upgrade_doesn_t_checkk_compatibility_and_rudder_cannot_start
branch
from
7f332c6
to
93cf813
Compare
https://issues.rudder.io/issues/16745