Project

General

Profile

Actions

Bug #7166

closed

Migrations to 3.1 may fail due to a wrong Jetty configuration migration on RPM based systems

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

Status:
Released
Priority:
1
Category:
Packaging
Target version:
Severity:
User visibility:
Effort required:
Priority:

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

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 PECCATTE2016-07-07Actions
Actions #1

Updated by Matthieu CERDA over 5 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 #2

Updated by Matthieu CERDA over 5 years ago

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

Updated by Matthieu CERDA over 5 years ago

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

Updated by Vincent MEMBRÉ over 5 years ago

  • Status changed from Pending release to Released

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

Actions #6

Updated by Nicolas CHARLES about 5 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

Also available in: Atom PDF