Project

General

Profile

Actions

Bug #19094

closed

Agents are unable to update after a configuration change in the interface

Added by Félix DALLIDET over 3 years ago. Updated over 3 years ago.

Status:
Resolved
Priority:
N/A
Assignee:
-
Category:
Server components
Target version:
Severity:
Major - prevents use of part of Rudder | no simple workaround
UX impact:
User visibility:
First impressions of Rudder
Effort required:
Priority:
99
Name check:
To do
Fix check:
To do
Regression:

Description

Currently the agents are unable to update their policies right after a change in the policies. It seems that the cf-serverd service on the Rudder server is always restarted after a change in the configuration. A restart can take up to ~10sec and if the agents try to update themselves in this time window, they will be unable to fetch their policies and so, will report on outdated policies, breaking the compliance.

error: No suitable server found
R: *********************************************************************************
* rudder-agent could not get an updated configuration from the policy server. *
* This can be caused by: *
* * 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. *
*********************************************************************************
error: No suitable server found
error: No suitable server found
R: *********************************************************************************
* rudder-agent could not get an updated configuration from the policy server. *
* This can be caused by: *
* * a networking issue *
* * an unavailable server *
* * the node changed policy server without running
* 'rudder agent server-keys-reset'
* * if the node's IP in not if the allowed networks of its policy server. *
* Any existing configuration policy will continue to be applied without change. *
*********************************************************************************
error: Rudder agent policies could not be updated.

And a grep of the restart on a short period of time:

Mar 25 09:19:36 server cf-serverd[31605]: CFEngine(server) rudder Doing a Graceful restart
Mar 25 09:19:36 server cf-serverd[31605]: rudder     info: Doing a Graceful restart
Mar 25 09:30:36 server cf-serverd[31961]: CFEngine(server) rudder Doing a Graceful restart
Mar 25 09:30:36 server cf-serverd[31961]: rudder     info: Doing a Graceful restart
Mar 25 09:33:29 server cf-serverd[2006]: rudder     info: Doing a Graceful restart
Mar 25 09:33:29 server cf-serverd[2006]: CFEngine(server) rudder Doing a Graceful restart
Mar 25 09:34:43 server cf-serverd[2534]: CFEngine(server) rudder Doing a Graceful restart
Mar 25 09:34:43 server cf-serverd[2534]: rudder     info: Doing a Graceful restart
Mar 25 09:49:40 server cf-serverd[2890]: CFEngine(server) rudder Doing a Graceful restart
Mar 25 09:49:40 server cf-serverd[2890]: rudder     info: Doing a Graceful restart
Mar 25 09:53:10 server cf-serverd[5634]: CFEngine(server) rudder Doing a Graceful restart
Mar 25 09:53:10 server cf-serverd[5634]: rudder     info: Doing a Graceful restart


Subtasks 7 (0 open7 closed)

Bug #19095: Remove 10s delay for restarting cf-serverdReleasedBenoît PECCATTEActions
Bug #19096: Reload cf-serverd only if neededReleasedAlexis MoussetActions
Bug #19112: reload cf-serverd only if file changedReleasedAlexis MoussetActions
Bug #19131: cf-serverd always reloadsReleasedFélix DALLIDETActions
Bug #19111: 2s delay when gracefule reloadingReleasedAlexis MoussetActions
Bug #19135: parent fix doesn't work at allReleasedAlexis MoussetActions
Bug #19136: Delay remote trigger on changeReleasedAlexis MoussetActions
Actions

Also available in: Atom PDF