Project

General

Profile

Actions
Copy link

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.

Status:
Released
Priority:
1 (highest)
Assignee:
Nicolas CHARLES
Category:
Packaging
Target version:
3.1.2
Pull Request:
https://github.com/Normation/rudder-p...
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:

Description

The correction introduced in #6930 is missing from the rudder-jetty specfile. It needs to be added as well in RPM Specfiles.

Related issues 2 (0 open — 2 closed)

Related to Rudder - Bug #6930: Upgrades to 3.1 fail due to a wrong /etc/default/rudder-jetty fileReleasedNicolas CHARLES2015-07-06Actions
Related to Rudder - Bug #8172: Upgrade from 2.11 to 3.1 on sles does not preserve the rudder-jetty java parametersReleasedBenoît PECCATTEActions
Actions
Copy link
 #1

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

Updated by Matthieu CERDA about 9 years ago

  • Related to Bug #6930: Upgrades to 3.1 fail due to a wrong /etc/default/rudder-jetty file added
Actions
Copy link
 #3

Updated by Matthieu CERDA about 9 years ago

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

Updated by Vincent MEMBRÉ about 9 years ago

  • Status changed from Pending release to Released

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

Actions
Copy link
 #6

Updated by Nicolas CHARLES over 8 years ago

  • Related to Bug #8172: Upgrade from 2.11 to 3.1 on sles does not preserve the rudder-jetty java parameters added
Actions
Copy link

Also available in: Atom PDF