Actions
Bug #4992
closed
Initial promises don't fetch new promises anymore on the policy server
Status:
Released
Priority:
1 (highest)
Assignee:
Jonathan CLARKE
Category:
System techniques
Target version:
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:
Description
Promises resynchronization on #4894 missed an essential part for the initial promises
Indeed, it adds the "failsafe" "!failsafe" part for updating only via failsafe.cf, however it did not introduced the modification necessary in failsafe.cf to effectively define this class.
Updated by Nicolas CHARLES over 10 years ago
- Status changed from In progress to Pending technical review
- Pull Request set to https://github.com/Normation/rudder-techniques/pull/405
PR is there: https://github.com/Normation/rudder-techniques/pull/405
This is a very nasty bug, that prevents the node from updating its promises
Updated by Nicolas CHARLES over 10 years ago
- Assignee changed from Nicolas CHARLES to Jonathan CLARKE
A workaround is to run the following command:
cf-agent -Kf failsafe.cf -Dfailsafe
Updated by Nicolas CHARLES over 10 years ago
- Status changed from Pending technical review to Pending release
- % Done changed from 0 to 100
Applied in changeset policy-templates:commit:0ad724acf265f863a7eb57491182361d2f10c52b.
Updated by Jonathan CLARKE over 10 years ago
Applied in changeset policy-templates:commit:ae094cca412362ff94212f7f5d6d64fc7cfe3c02.
Updated by Vincent MEMBRÉ over 10 years ago
- Status changed from Pending release to Released
This bug has been fixed in Rudder versions that were released today.
- 2.9.6 (announcement , changelog)
- 2.10.2 (announcement , changelog)
- Download information: https://www.rudder-project.org/site/get-rudder/downloads/
Actions