Bug #17878
closedAll plugins are disabled after a minor upgrade
Description
When doing a minor upgrade of the server, all plugins are disabled before the upgrade and not re-enabled afterward.
This is very misleading for the users.
It displays the following error message:
******************************************************************************** Due to incompatibility reasons for this specific version all plugins have been disabled. Make sure to update your repo index and install the latest version of your plugins before re-enabling them. You can use the following commands to upgrade your plugins: rudder package update rudder package upgrade-all ********************************************************************************
But running the given commands will not solve anything when applying a minor update.
It will only work on major ones.
It happens when upgrading from 6.0.6 to 6.0.8-nightly
But the plugins should not be changed in a minor update. I think this is an unclean workaround when we broke plugin compatibility in 6.0.4.We should most likely either:
- State than an upgrade disabled all plugins and let the user re-enabled them manually
- Save the plugin state before update and try to re-enable them. This need to differentiate the minor upgrades from the major ones.
Updated by Nicolas CHARLES over 4 years ago
- Related to Bug #16792: When upgrading to 6.0.3 the packaging should disable all installed plugins added
Updated by François ARMAND over 4 years ago
- Severity changed from Minor - inconvenience | misleading | easy workaround to Major - prevents use of part of Rudder | no simple workaround
- Priority changed from 80 to 100
The workaround is not easy.
We need to:
- correct message and add "rudder package enable or enable-all" to re-enable plugins and then "rudder upgrade-all"
- for 6.1: keep plugins enable
- for minor updates: we would like to automatically update plugins to good version
So, the general logic is:
- keep which plugins were enable before upgrade,
- re-enable plugins after upgrade && upgrade all
Updated by Vincent MEMBRÉ about 4 years ago
- Target version set to 6.1.6
- Priority changed from 100 to 96
Updated by Vincent MEMBRÉ about 4 years ago
- Status changed from New to In progress
- Assignee changed from Félix DALLIDET to Vincent MEMBRÉ
Updated by Vincent MEMBRÉ about 4 years ago
- Assignee changed from Vincent MEMBRÉ to Alexis Mousset
- Pull Request set to https://github.com/Normation/rudder-packages/pull/2368
Updated by Vincent MEMBRÉ about 4 years ago
- Status changed from In progress to Pending technical review
- Assignee changed from Alexis Mousset to Félix DALLIDET
Updated by Vincent MEMBRÉ about 4 years ago
- Target version changed from 6.1.6 to 6.2.0~beta1
Updated by Vincent MEMBRÉ about 4 years ago
- Assignee changed from Félix DALLIDET to Alexis Mousset
- Priority changed from 96 to 95
Updated by Vincent MEMBRÉ about 4 years ago
- Assignee changed from Alexis Mousset to Félix DALLIDET
Updated by Vincent MEMBRÉ about 4 years ago
- Assignee changed from Félix DALLIDET to Alexis Mousset
Updated by Vincent MEMBRÉ about 4 years ago
- Status changed from Pending technical review to Pending release
Applied in changeset rudder-packages|3ed1d8fe5f7293233c0ebab8883b271911331bf4.
Updated by Vincent MEMBRÉ about 4 years ago
- Status changed from Pending release to Released
This bug has been fixed in Rudder 6.2.0~beta1 which was released today.
Updated by Elaad FURREEDAN almost 4 years ago
- Priority changed from 95 to 94
- Fix check changed from To do to Checked