Actions
Bug #26897
closed
rudder server reload-techniques should work even if webapp is stopped
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
0
Name check:
To do
Fix check:
Checked
Regression:
No
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
Updated by François ARMAND about 1 month ago
- 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.
Updated by François ARMAND about 1 month ago
- Priority changed from To review to 1 (highest)
P1 because short.
Updated by Benoît PECCATTE 29 days ago
- 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
Updated by Benoît PECCATTE 18 days ago
- Status changed from Pending technical review to Pending release
Applied in changeset rudder-agent|40f9614c3b6cfdec15dd40c2df47f5cdeb3b615c.
Updated by François ARMAND 18 days ago
- File clipboard-202506031202-0tpi6.png clipboard-202506031202-0tpi6.png added
- Fix check changed from To do to Checked
Updated by Vincent MEMBRÉ 16 days ago
- 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.
Actions