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
Added by François ARMAND about 7 years ago.
Updated about 7 years ago.
Category:
System integration
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.
- Assignee set to François ARMAND
- 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
- 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
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"
- Status changed from Pending technical review to Pending release
- 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.
Also available in: Atom
PDF
Updated by 
Updated by