Project

General

Profile

Actions

Bug #8172

closed

Upgrade from 2.11 to 3.1 on sles does not preserve the rudder-jetty java parameters

Added by Nicolas CHARLES about 5 years ago. Updated almost 5 years ago.

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

Description

On SLES11, upgrading from 2.11 to 3.1 on SLES 11 failed to preserve the configured java parameters, and restored default config file (with only 1 GB allocated to webapp)


Subtasks 1 (0 open1 closed)

Bug #8648: Previous merge broke a binary file: rsyslog-4.8.0.tar.bz2ReleasedAlexis MOUSSET2016-07-07Actions

Related issues

Related to Rudder - Bug #6773: Rudder-ldap and rudder-jetty settings should be user configurable in /etc/defaultReleasedBenoît PECCATTE2015-06-19Actions
Related to Rudder - Bug #7850: Upgrading from 2.11 to 3.1.6, with a distributed setup ( external DB ), on SLES, leads to invalid config file for LDAPRejectedActions
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
Related to Rudder - Bug #8418: Configuration files do not get updated when user has modified the stock onesNewActions
Actions #1

Updated by Nicolas CHARLES about 5 years ago

  • Related to Bug #6773: Rudder-ldap and rudder-jetty settings should be user configurable in /etc/default added
Actions #2

Updated by Nicolas CHARLES about 5 years ago

  • Related to Bug #7850: Upgrading from 2.11 to 3.1.6, with a distributed setup ( external DB ), on SLES, leads to invalid config file for LDAP added
Actions #3

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

Updated by Nicolas CHARLES about 5 years ago

  • Tags set to Sponsored
  • Priority changed from N/A to 1
Actions #5

Updated by François ARMAND about 5 years ago

Could you specify what are the files that are reverted, and that should not ?

There is a multitude of way to change these parameter, a specific case would help understand the problem.

Actions #6

Updated by Nicolas CHARLES about 5 years ago

  • Assignee set to Benoît PECCATTE

In pré-3.1, conf file for rudder-jetty was user modifiable in /opt/rudder/etc/rudder-jetty.conf; starting of 3.1 it is /etc/default/rudder-jetty.conf

If user configured something in /opt/rudder/etc/rudder-jetty.conf, it is lost in upgrade to 3.1 - at least for SLES - as /etc/default/rudder-jetty.conf contain only default content

Related ticket #7850 states the same for slapd config file

Actions #7

Updated by François ARMAND about 5 years ago

  • Tags changed from Sponsored to Sponsored, Next minor release

This is important and should be simple to correct.

Actions #8

Updated by Benoît PECCATTE about 5 years ago

I need to reproduce this since there is already code to migrate these parameters on sles, we need more informations to identify this bug

Actions #9

Updated by Benoît PECCATTE about 5 years ago

  • Assignee changed from Benoît PECCATTE to Nicolas CHARLES

I cannot reproduce, I just tested on a fresh install
- rudder 2.11 on SLES 11
- change jetty settings
- upgrade rudder to 3.1

-> setting are properly restored in /etc/default/rudder-jetty.conf

Could you elaborate a bit more on how to reproduce ?

Actions #10

Updated by Nicolas CHARLES about 5 years ago

  • Assignee changed from Nicolas CHARLES to Benoît PECCATTE

It appeared twice:
once in an upgrade from 2.11.8 to 3.1.1, upon upgrade, XMX value was lost
once in distributed setup (remote rudder-reports), upgrading from 2.11.8 to 3.1.3
both on sles11

Actions #11

Updated by Vincent MEMBRÉ almost 5 years ago

  • Target version changed from 3.1.10 to 3.1.11
Actions #12

Updated by Nicolas CHARLES almost 5 years ago

It seemed it appeared also on an upgrade from 3.1.6 to 3.1.10 on SLES11

Actions #13

Updated by Vincent MEMBRÉ almost 5 years ago

  • Target version changed from 3.1.11 to 3.1.12
Actions #14

Updated by François ARMAND almost 5 years ago

  • Related to Bug #8418: Configuration files do not get updated when user has modified the stock ones added
Actions #15

Updated by Nicolas CHARLES almost 5 years ago

It may be related to the conffiles ticket that was handled recently

Actions #16

Updated by Benoît PECCATTE almost 5 years ago

  • Status changed from New to In progress
Actions #17

Updated by Benoît PECCATTE almost 5 years ago

  • Status changed from In progress to Pending technical review
  • Assignee changed from Benoît PECCATTE to Jonathan CLARKE
  • Pull Request set to https://github.com/Normation/rudder-packages/pull/986
Actions #18

Updated by François ARMAND almost 5 years ago

  • Assignee changed from Jonathan CLARKE to François ARMAND

I'm merging that, Jon doesn't have any added value on it.

We need a linter for that :/

Actions #19

Updated by François ARMAND almost 5 years ago

Benoit, could you upmerge it please?

Actions #20

Updated by François ARMAND almost 5 years ago

  • Assignee changed from François ARMAND to Benoît PECCATTE
Actions #21

Updated by Benoît PECCATTE almost 5 years ago

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

Updated by Alexis MOUSSET almost 5 years ago

  • Status changed from Pending release to Released

This bug has been fixed in Rudder 3.1.12 and 3.2.5 which were released today.

Actions

Also available in: Atom PDF