Actions
Bug #4995
closed
Server with no nodes can't update its promises
Status:
Rejected
Priority:
1 (highest)
Assignee:
Category:
Web - Config management
Target version:
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:
Description
I have installed a fresh server with no nodes and directly updated my policies
The promise generation should have been very short (instant) but it does not seems to end.
I restart the webapp, and still the same behavior.
In debug logs I found that a system variable (CLIENTSFOLDER) does not exists since there is no nodes attached to my server and is the last log line I have.
Here is the output:
[2014-06-11 10:31:57] INFO com.normation.rudder.services.policies.DeploymentServiceImpl - Start policy generation, checking updated rules [2014-06-11 10:31:57] DEBUG com.normation.rudder.services.policies.DeploymentServiceImpl - All relevant information fetched in 400ms, start names historization. [2014-06-11 10:31:57] DEBUG com.normation.rudder.services.policies.DeploymentServiceImpl - Historization of names done in 397ms, start to build rule values. [2014-06-11 10:31:57] DEBUG com.normation.rudder.services.policies.DeploymentServiceImpl - RuleVals built in 25ms, start to expand their values. [2014-06-11 10:31:57] DEBUG com.normation.rudder.services.policies.DeploymentServiceImpl - RuleVals expanded in 29ms, start to build global system variables. [2014-06-11 10:31:57] DEBUG com.normation.rudder.services.policies.DeploymentServiceImpl - Global system variables built in 29ms, start to build new node configurations. [2014-06-11 10:31:58] DEBUG com.normation.rudder.services.policies.DeploymentServiceImpl - Node's target configuration built in 329, start to update rule values. [2014-06-11 10:31:58] DEBUG com.normation.rudder.services.policies.DeploymentServiceImpl - RuleVals updated in 62 millisec, start to detect changes in node configuration. [2014-06-11 10:31:58] DEBUG com.normation.rudder.services.policies.DeploymentServiceImpl - Checked node configuration updates leading to rules serial number updates and serial number updated in 51ms [2014-06-11 10:31:58] INFO com.normation.rudder.services.policies.nodeconfig.NodeConfigurationServiceImpl - Configuration of following nodes were updated, their promises are going to be written: [root] [2014-06-11 10:31:58] DEBUG com.normation.rudder.services.policies.RudderCf3PromisesFileWriterServiceImpl - 37 promises templates read in 478ms [2014-06-11 10:31:58] DEBUG com.normation.rudder.services.policies.RudderCf3PromisesFileWriterServiceImpl - Writting promises for node 'server.rudder.local' (root) [2014-06-11 10:31:58] DEBUG com.normation.rudder.services.policies.RudderCf3PromisesFileWriterServiceImpl - Preparing the PI variables for container /var/rudder/cfengine-community/inputs.new [2014-06-11 10:31:58] DEBUG com.normation.rudder.services.policies.RudderCf3PromisesFileWriterServiceImpl - Variable system named CLIENTSFOLDERS not found in the extended variables environnement
Updated by Vincent MEMBRÉ over 10 years ago
I tried on a new install still with no nodes (One was pending though ... ) And there was no problem
[2014-06-11 11:47:48] DEBUG com.normation.rudder.services.policies.DeploymentServiceImpl - All relevant information fetched in 366ms, start names historization. [2014-06-11 11:47:48] DEBUG com.normation.rudder.services.policies.DeploymentServiceImpl - Historization of names done in 427ms, start to build rule values. [2014-06-11 11:47:48] DEBUG com.normation.rudder.services.policies.DeploymentServiceImpl - RuleVals built in 34ms, start to expand their values. [2014-06-11 11:47:48] DEBUG com.normation.rudder.services.policies.DeploymentServiceImpl - RuleVals expanded in 31ms, start to build global system variables. [2014-06-11 11:47:48] DEBUG com.normation.rudder.services.policies.DeploymentServiceImpl - Global system variables built in 31ms, start to build new node configurations. [2014-06-11 11:47:48] DEBUG com.normation.rudder.services.policies.DeploymentServiceImpl - Node's target configuration built in 298, start to update rule values. [2014-06-11 11:47:49] DEBUG com.normation.rudder.services.policies.DeploymentServiceImpl - RuleVals updated in 113 millisec, start to detect changes in node configuration. [2014-06-11 11:47:49] DEBUG com.normation.rudder.services.policies.DeploymentServiceImpl - Checked node configuration updates leading to rules serial number updates and serial number updated in 15ms [2014-06-11 11:47:49] INFO com.normation.rudder.services.policies.nodeconfig.NodeConfigurationServiceImpl - Configuration of following nodes were updated, their promises are going to be written: [root] [2014-06-11 11:47:49] DEBUG com.normation.rudder.services.policies.RudderCf3PromisesFileWriterServiceImpl - 37 promises templates read in 421ms [2014-06-11 11:47:49] DEBUG com.normation.rudder.services.policies.RudderCf3PromisesFileWriterServiceImpl - Writting promises for node 'server.rudder.local' (root) [2014-06-11 11:47:49] DEBUG com.normation.rudder.services.policies.RudderCf3PromisesFileWriterServiceImpl - Preparing the PI variables for container /var/rudder/cfengine-community/inputs.new [2014-06-11 11:47:49] DEBUG com.normation.rudder.services.policies.RudderCf3PromisesFileWriterServiceImpl - Variable system named CLIENTSFOLDERS not found in the extended variables environnement [2014-06-11 11:47:51] DEBUG com.normation.rudder.services.policies.RudderCf3PromisesFileWriterServiceImpl - ` Execute cf-promise for '/var/rudder/cfengine-community/inputs.new': 1132ms (1s) [2014-06-11 11:47:51] DEBUG com.normation.rudder.services.policies.RudderCf3PromisesFileWriterServiceImpl - Backuping old promises from /var/rudder/cfengine-community/inputs to /var/rudder/cfengine-community/inputs.bkp [2014-06-11 11:47:51] DEBUG com.normation.rudder.services.policies.RudderCf3PromisesFileWriterServiceImpl - Copying new promises into /var/rudder/cfengine-community/inputs [2014-06-11 11:47:51] DEBUG com.normation.rudder.services.policies.RudderCf3PromisesFileWriterServiceImpl - Moving folders from /var/rudder/cfengine-community/inputs.new to /var/rudder/cfengine-community/inputs [2014-06-11 11:47:51] DEBUG com.normation.rudder.services.policies.DeploymentServiceImpl - Node configuration written on filesystem in 1966 millisec. [2014-06-11 11:47:51] DEBUG com.normation.rudder.services.policies.DeploymentServiceImpl - Node configuration cached in LDAP in 17 millisec. [2014-06-11 11:47:51] DEBUG com.normation.rudder.services.policies.DeploymentServiceImpl - Node configuration written in 1989ms, start to update expected reports. [2014-06-11 11:47:51] DEBUG com.normation.rudder.services.policies.DeploymentServiceImpl - Reports updated in 13ms [2014-06-11 11:47:51] DEBUG com.normation.rudder.services.policies.DeploymentServiceImpl - Timing summary: [2014-06-11 11:47:51] DEBUG com.normation.rudder.services.policies.DeploymentServiceImpl - Fetch all information : 366 ms [2014-06-11 11:47:51] DEBUG com.normation.rudder.services.policies.DeploymentServiceImpl - Historize names : 427 ms [2014-06-11 11:47:51] DEBUG com.normation.rudder.services.policies.DeploymentServiceImpl - Build current rule values : 34 ms [2014-06-11 11:47:51] DEBUG com.normation.rudder.services.policies.DeploymentServiceImpl - Expand rule parameters : 31 ms [2014-06-11 11:47:51] DEBUG com.normation.rudder.services.policies.DeploymentServiceImpl - Build target configuration: 298 ms [2014-06-11 11:47:51] DEBUG com.normation.rudder.services.policies.DeploymentServiceImpl - Update rule vals : 113 ms [2014-06-11 11:47:51] DEBUG com.normation.rudder.services.policies.DeploymentServiceImpl - Increment rule serials : 15 ms [2014-06-11 11:47:51] DEBUG com.normation.rudder.services.policies.DeploymentServiceImpl - Write node configurations : 1989 ms [2014-06-11 11:47:51] DEBUG com.normation.rudder.services.policies.DeploymentServiceImpl - Save expected reports : 13 ms [2014-06-11 11:47:51] DEBUG com.normation.rudder.services.policies.DeploymentServiceImpl - Policy generation completed in 3392 millisec [2014-06-11 11:47:51] INFO com.normation.rudder.batch.AsyncDeploymentAgent - Successful policy update '3' [started 2014-06-11 11:47:47 - ended 2014-06-11 11:47:51]
I guess that something went wrong with cf-promises ... on the first server
I had dns issue on my first server maybe making the cf-promises very loooong
Updated by Vincent MEMBRÉ over 10 years ago
- Status changed from New to Rejected
It was a DNS issue ... cf-promises (and cf-agent) could not resolve my server hostname ...
Updated by Benoît PECCATTE almost 10 years ago
- Category changed from 14 to Web - Config management
Actions