Bug #4288
closed
ncf promises may not be correctly updated leading to faulty update promises on policy server
Added by Nicolas CHARLES almost 11 years ago.
Updated over 9 years ago.
Description
NCf framework is updated independently from the Rudder promises
On every node, we make a find on /var/rudder/ncf to load ncf promises
However, /var/rudder/ncf is copied from /usr/share/ncf/tree via the client-server connectivity
If we have new promises, that relies on a change in /var/rudder/ncf, but that didn't have time to be propagated, it will never succeed, and make the cf-serverd unworkable.
On the policy server, we should rely on local copy for updating ncf to prevent this issue
- Status changed from In progress to Pending technical review
- Assignee changed from Nicolas CHARLES to Jonathan CLARKE
- Pull Request set to https://github.com/Normation/rudder-techniques/pull/261
- Assignee changed from Jonathan CLARKE to Matthieu CERDA
Reassigning to MCE as JCL is on hollidays and it's a blocker for 2.9.0 release.
- Status changed from Pending technical review to Pending release
- % Done changed from 0 to 100
Applied in changeset commit:7545fa261cd76c8c8fc4dcd158f3f9d76209c8e1.
Applied in changeset commit:08617d8850fb91964e50f3f278312f03c36e9692.
[STAMP] Approved, i love this.
- Subject changed from Promises on policy server can stay invalid due to race condition in promise update/ncf update to ncf promises may not be correctly updated leading to faulty update promises on policy server
- Status changed from Pending release to Released
This bug has been fixed in Rudder 2.9.0, which was released today.
Check out:
- Project changed from 24 to Rudder
- Category changed from Techniques to Techniques
Also available in: Atom
PDF