ncf promises may not be correctly updated leading to faulty update promises on policy server
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
Updated by Matthieu CERDA about 6 years ago
- Status changed from Pending release to Released
This bug has been fixed in Rudder 2.9.0, which was released today.
- The release announcement: http://www.rudder-project.org/pipermail/rudder-announce/2013-December/000067.html * The full ChangeLog: http://www.rudder-project.org/foswiki/bin/view/System/Documentation:ChangeLog29 * Download information: https://www.rudder-project.org/site/get-rudder/downloads/