Actions
Bug #2807
closed
After a migration from 2.3 to 2.4.0~beta3, Rudder webapp isn't functional until jetty is restarted
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:
Description
On SLES, if Rudder webapp is up during the upgrade, Rudder webapp seems not functional until the restart of jetty. If not, Rudder will not be started after the upgrade.
Updated by Jonathan CLARKE about 12 years ago
- Status changed from New to 2
- Assignee changed from Nicolas PERRON to Jonathan CLARKE
- Target version changed from 2.4.0~beta4 to 2.4.0~beta5
Let's start by adding an echo to warn the user they have to restart rudder-jetty.
Updated by Jonathan CLARKE about 12 years ago
- Status changed from 2 to In progress
The reason that we don't restart jetty from the RPM postinst script is because we ran into a bug with this, where the jetty init script caused the whole RPM process to hang indefinitely...
Updated by Jonathan CLARKE about 12 years ago
- Subject changed from After a migration from 2.3 to 2.4.0~beta3, Rudder webapp isn't functionnal until jetty is restarted. to After a migration from 2.3 to 2.4.0~beta3, Rudder webapp isn't functional until jetty is restarted
Updated by Jonathan CLARKE about 12 years ago
- Status changed from In progress to Pending technical review
- % Done changed from 0 to 100
Applied in changeset commit:950fa0efb2d3ad40fcf355d2943e4ad7c3967746.
Updated by Jonathan CLARKE about 12 years ago
- Status changed from Pending technical review to Released
Updated by Nicolas PERRON almost 12 years ago
- Project changed from Rudder to 34
- Category deleted (
11)
Updated by Benoît PECCATTE over 9 years ago
- Project changed from 34 to Rudder
- Category set to Packaging
Updated by Benoît PECCATTE over 7 years ago
- Related to Architecture #9820: Stop jetty before upgrading the webapp added
Actions