Bug #8172: Upgrade from 2.11 to 3.1 on sles does not preserve the rudder-jetty java parameters - Rudder - Issue Tracker

Custom queries

8.1 beta
Bugs triage
CS - by priority
CS - to review
My TR
Need technical review
Open bugs (all)
Open bugs (UI - UX)
Open UX defects (all)
Opened by users

Actions

Copy link

Bug #8172

closed

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

Added by Nicolas CHARLES over 8 years ago. Updated over 2 years ago.

Status:

Released

Priority:

1 (highest)

Assignee:

Benoît PECCATTE

Category:

Server components

Target version:

3.1.12

Pull Request:

https://github.com/Normation/rudder-p...

Severity:

UX impact:

User visibility:

Effort required:

Priority:

Name check:

Fix check:

Regression:

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 open — 1 closed)

Bug #8648: Previous merge broke a binary file: rsyslog-4.8.0.tar.bz2

Released

Alexis Mousset

2016-07-07

Actions

Related issues 4 (1 open — 3 closed)

Related to Rudder - Bug #6773: Rudder-ldap and rudder-jetty settings should be user configurable in /etc/default	Released	Benoît PECCATTE	2015-06-19	Actions
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 LDAP	Rejected			Actions
Related to Rudder - Bug #7166: Migrations to 3.1 may fail due to a wrong Jetty configuration migration on RPM based systems	Released	Nicolas CHARLES	2015-09-04	Actions
Related to Rudder - Bug #8418: Configuration files do not get updated when user has modified the stock ones	New			Actions

Issue # Delay: days Cancel

History
Notes
Property changes
Associated revisions

Actions

Copy link

Updated by Nicolas CHARLES over 8 years ago

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

Actions

Copy link

Updated by Nicolas CHARLES over 8 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

Copy link

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

Copy link

Updated by Nicolas CHARLES over 8 years ago

Translation missing: en.field_tag_list set to Sponsored
Priority changed from N/A to 1 (highest)

Actions

Copy link

Updated by François ARMAND over 8 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

Copy link

Updated by Nicolas CHARLES over 8 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

Copy link

Updated by François ARMAND over 8 years ago

Translation missing: en.field_tag_list changed from Sponsored to Sponsored, Next minor release

This is important and should be simple to correct.

Actions

Copy link

Updated by Benoît PECCATTE over 8 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

Copy link

Updated by Benoît PECCATTE over 8 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

Copy link

#10

Updated by Nicolas CHARLES over 8 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

Copy link

#11