Bug #11622
Updated by Alexis Mousset about 7 years ago
If a node is able to access the system policy but not it's own: It's still saying, at the same time, that the update failed and that they were updated. This has been wrong since the rudder wrapper got added. <pre> # rudder agent update R: ********************************************************************************* * rudder-agent could not get an updated configuration from the policy server. * * This can be caused by: * * * an incorrect DNS resolution of this node * * * an agent key that has been changed * * * if this node is not accepted or deleted node on the Rudder root server * * * if this node has changed policy server without sending a new inventory * * Any existing configuration policy will continue to be applied without change. * ********************************************************************************* ok: Rudder agent promises were updated. </pre>