Architecture #9820
closed
Stop jetty before upgrading the webapp
Added by Benoît PECCATTE almost 8 years ago.
Updated over 7 years ago.
Description
When we upgrade the rudder webapp, we let jetty running during the upgrade.
This could lead to subtle bugs.
A better approach would be to stop jetty pre-upgrade and start it post-upgrade.
In all case, Jetty MUST be AT LEAST restarted when the war change, else it WILL lead to problems.
- Target version changed from 4.1.0~beta1 to 4.1.0~beta2
- Target version changed from 4.1.0~beta2 to 4.1.0~beta3
- Target version changed from 4.1.0~beta3 to 4.1.0~rc1
- Description updated (diff)
- Assignee set to Benoît PECCATTE
- Translation missing: en.field_tag_list set to Blocking 4.1
- Status changed from New to In progress
- Status changed from In progress to Pending technical review
- Assignee changed from Benoît PECCATTE to Alexis Mousset
- Pull Request set to https://github.com/Normation/rudder-packages/pull/1273
- Related to Bug #2807: After a migration from 2.3 to 2.4.0~beta3, Rudder webapp isn't functional until jetty is restarted added
- Status changed from Pending technical review to Pending release
- Status changed from Pending release to Released
This bug has been fixed in Rudder 4.1.0~rc1 which was released today.
- Related to Bug #10531: When upgrading Rudder to 4.1 on debian8, the web interface is not restarted after properties are modified, so it fails to run added
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by 
Updated by