Bug #16735: When upgrading from 5.0 to 6.0 (on centos7), incompatible plugins are not disabled - Rudder - Issue Tracker

Actions

Copy link

Bug #16735

closed

When upgrading from 5.0 to 6.0 (on centos7), incompatible plugins are not disabled

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

Status:

Released

Priority:

N/A

Assignee:

Alexis Mousset

Category:

Packaging

Target version:

6.0.3

Pull Request:

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

Severity:

UX impact:

User visibility:

Effort required:

Priority:

Name check:

Reviewed

Fix check:

Error - Blocking

Regression:

Description

Yet /opt/rudder/bin/rudder-upgrade seems to be ran

Subtasks 1 (0 open — 1 closed)

Actions

Copy link

Updated by Nicolas CHARLES almost 5 years ago

Subject changed from When upgrading from 5.0 to 6.0 (on centos7), plugins are not disabled to When upgrading from 5.0 to 6.0 (on centos7), incompatible plugins are not disabled

Actions

Copy link

Updated by Nicolas CHARLES almost 5 years ago

Rudder upgrade does diesable them, yet the postinst does

if [ -f /tmp/rudder-plugins-upgrade ]
then
  /opt/rudder/bin/rudder-pkg plugin restore-status < /tmp/rudder-plugins-upgrade
fi

Actions

Copy link

Updated by Nicolas CHARLES almost 5 years ago

Status changed from New to In progress
Assignee set to Nicolas CHARLES

Actions

Copy link

Updated by Nicolas CHARLES almost 5 years ago

Assignee changed from Nicolas CHARLES to Alexis Mousset
Pull Request set to https://github.com/Normation/rudder-packages/pull/2200

PR https://github.com/Normation/rudder-packages/pull/2200

Actions

Copy link

Updated by Vincent MEMBRÉ almost 5 years ago

Target version changed from 6.0.3 to 6.0.4

Actions

Copy link

Updated by Nicolas CHARLES almost 5 years ago

Status changed from In progress to Pending release

Applied in changeset rudder-packages|3e6d8ead5edbe042a6db5936fed9f5544d845f51.

Actions

Copy link

Updated by Nicolas CHARLES almost 5 years ago

Applied in changeset rudder-packages|b9b505adf9e9b1bbb7b85baa80d8d8a0536428f5.

Actions

Copy link

Updated by Nicolas CHARLES almost 5 years ago

ok, now it fails because rudder-jetty cannot be restarted

INFO: rudder-server-relay setup complete.
  Installing : 1398866025:rudder-webapp-6.0.3.rc1.git202002180103-1.EL.7.x86_64                                                                                                                                                         16/32 
warning: /opt/rudder/etc/openldap/slapd.conf created as /opt/rudder/etc/openldap/slapd.conf.rpmnew
warning: /opt/rudder/etc/rudder-web.properties created as /opt/rudder/etc/rudder-web.properties.rpmnew
warning: user rudder-slapd does not exist - using root
warning: group rudder-slapd does not exist - using root
INFO: Creating groups ...INFO: Creating users ... Done
INFO: Setting up systemd ...Created symlink from /etc/systemd/system/multi-user.target.wants/rudder-jetty.service to /usr/lib/systemd/system/rudder-jetty.service.
Created symlink from /etc/systemd/system/rudder-server.service.requires/rudder-jetty.service to /usr/lib/systemd/system/rudder-jetty.service.
Created symlink from /etc/systemd/system/multi-user.target.wants/rudder-slapd.service to /usr/lib/systemd/system/rudder-slapd.service.
Created symlink from /etc/systemd/system/rudder-server.service.requires/rudder-slapd.service to /usr/lib/systemd/system/rudder-slapd.service.
INFO: Restarting rudder-slapd... Done
enable /opt/rudder/share/plugins/scale-out-relay/scale-out-relay.jar
[]
Restarting jetty
 $ service rudder-jetty restart
Stopping Jetty: ERROR: no pid found at /var/rudder/run/rudder-jetty.pid
Setting umask to 0007
Starting Jetty: already running.
done
INFO: Launching script to check if a migration is needed ...
Done

Actions

Copy link