Bug #7166
closed
Migrations to 3.1 may fail due to a wrong Jetty configuration migration on RPM based systems
Added by Matthieu CERDA about 9 years ago.
Updated about 9 years ago.
Description
The correction introduced in #6930 is missing from the rudder-jetty specfile. It needs to be added as well in RPM Specfiles.
- Status changed from In progress to Pending technical review
- Assignee changed from Matthieu CERDA to Nicolas CHARLES
- Pull Request set to https://github.com/Normation/rudder-packages/pull/745
- Related to Bug #6930: Upgrades to 3.1 fail due to a wrong /etc/default/rudder-jetty file added
- Status changed from Pending technical review to Pending release
- % Done changed from 0 to 100
- Status changed from Pending release to Released
This bug has been fixed in Rudder 3.1.2 which was released today.
- Related to Bug #8172: Upgrade from 2.11 to 3.1 on sles does not preserve the rudder-jetty java parameters added
Also available in: Atom
PDF
Updated by Matthieu CERDA 
Updated by 
Updated by