Project

General

Profile

Actions
Copy link

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

Added by Matthieu CERDA over 9 years ago. Updated over 9 years ago.

Status:
Released
Priority:
1 (highest)
Assignee:
Nicolas CHARLES
Category:
System integration
Target version:
3.1.0
Pull Request:
https://github.com/Normation/rudder-p...
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:

Related issues 1 (0 open — 1 closed)

Related to Rudder - Bug #7166: Migrations to 3.1 may fail due to a wrong Jetty configuration migration on RPM based systemsReleasedNicolas CHARLES2015-09-04Actions
Actions
Copy link
 #1

Updated by Matthieu CERDA over 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
Actions
Copy link
 #2

Updated by Matthieu CERDA over 9 years ago

  • Status changed from Pending technical review to Pending release
  • % Done changed from 0 to 100
Actions
Copy link
 #4

Updated by Vincent MEMBRÉ over 9 years ago

  • Parent task set to #6773
Actions
Copy link
 #5

Updated by Vincent MEMBRÉ over 9 years ago

  • Status changed from Pending release to Released

This bug has been fixed in Rudder 3.1.0 which was released today.

Actions
Copy link
 #6

Updated by Matthieu CERDA about 9 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
Copy link

Also available in: Atom PDF