Actions
Bug #10418
closed
Bug #10379: When upgrading to 4.1, rudder.community.checkpromises.command=/bin/true option is lost
checkpromise+sighup config should be commented in properties file and bad name of corresponding hook
Bug #10418:
checkpromise+sighup config should be commented in properties file and bad name of corresponding hook
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
0
Name check:
Fix check:
Regression:
Description
As explain in comment in the parent task, they are no more used and it is misleading to keep them uncommented. And it breaks the migration script logic.
Updated by François ARMAND almost 9 years ago
- Assignee set to François ARMAND
Updated by François ARMAND almost 9 years ago
- Status changed from In progress to Pending technical review
- Assignee changed from François ARMAND to Benoît PECCATTE
- Pull Request set to https://github.com/Normation/rudder/pull/1586
Updated by François ARMAND almost 9 years ago
- Subject changed from checkpromise config should be commented in properties file to checkpromise+sighup config should be commented in properties file and bad name of corresponding hook
Updated by François ARMAND almost 9 years ago
Also, file "/opt/rudder/hooks.d/policy-generation-finished/50-sigup-cf-serverd" should be named "/opt/rudder/hooks.d/policy-generation-finished/50-reload-policy-file-server"
Updated by François ARMAND almost 9 years ago
- Status changed from Pending technical review to Pending release
Applied in changeset rudder|a89ba73e668293e48d2dc5c7431e45212b427db8.
Updated by Benoît PECCATTE almost 9 years ago
- Status changed from Pending release to Released
- Priority set to 0
This bug has been fixed in Rudder 4.1.0 which was released today.
- 4.1.0: Announce Changelog
- Download: https://www.rudder-project.org/site/get-rudder/downloads/
Actions