Bug #26897
closed
rudder server reload-techniques should work even if webapp is stopped
Added by Nicolas CHARLES about 1 month ago.
Updated 16 days ago.
Description
This command is used during some plugin upgrades, when webapp can be down, and break upgrades - it could also cause problems during policy synchronisation
We have a dedicated flag file for this use case: /opt/rudder/etc/force_technique_reload
So we should detect if webapp is running, and if not, touch the flag file and not fail
Files
- Assignee set to Benoît PECCATTE
Idea: the command needs to check if rudder is live or not.
- if rudder is live, then do as today (call the api),
- else touch the file flag.
We can do the same as rudder server trigger-policy-generation
which does almost that.
- Priority changed from To review to 1 (highest)
- Status changed from New to In progress
- Status changed from In progress to Pending technical review
- Assignee changed from Benoît PECCATTE to Alexis Mousset
- Pull Request set to https://github.com/Normation/rudder-agent/pull/417
- Status changed from Pending technical review to Pending release
On restart:

- Status changed from Pending release to Released
This bug has been fixed in Rudder 8.2.7 and 8.3.2 which were released today.
Also available in: Atom
PDF