Actions
Bug #6930
closed
Bug #6773: Rudder-ldap and rudder-jetty settings should be user configurable in /etc/default
Upgrades to 3.1 fail due to a wrong /etc/default/rudder-jetty file
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:
Description
After the upgrade, this file contains the following wrong statements:
# Memory settings
#
# The defaults should be enough for up to ~100 nodes
#
JAVA_XMX=${JAVA_XMX:
JAVA_MAXPERMSIZE=${JAVA_MAXPERMSIZE:
Updated by Matthieu CERDA almost 9 years ago
- 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/704
Updated by Matthieu CERDA almost 9 years ago
- Status changed from Pending technical review to Pending release
- % Done changed from 0 to 100
Applied in changeset rudder-packages|c793213f59c4e2dc57423b02b63d11bdab786fa7.
Updated by Nicolas CHARLES almost 9 years ago
Applied in changeset rudder-packages|b9a790624bf6dc664d24c0d7e0bb5031216d57a6.
Updated by Vincent MEMBRÉ almost 9 years ago
- Status changed from Pending release to Released
This bug has been fixed in Rudder 3.1.0 which was released today.
- Announcement 3.1
- Changelog 3.1
- Download information: https://www.rudder-project.org/site/get-rudder/downloads/
Updated by Matthieu CERDA over 8 years ago
- Related to Bug #7166: Migrations to 3.1 may fail due to a wrong Jetty configuration migration on RPM based systems added
Actions