Project

General

Profile

Actions

Bug #6113

closed

When we install rudder-agent package, it tries to send automatically the node inventory to machine "rudder"

Added by Nicolas CHARLES about 9 years ago. Updated about 9 years ago.

Status:
Released
Priority:
3
Category:
System techniques
Target version:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:

Description

I've been installing several rudder-agent on debian vagrant boxes, and each time, the inventory was not automatically sent
The content of the output folder contain :

2015-01-09T09:00:44+0000    error: /default/update/methods/'update'[0]: Method 'update_action' failed in some repairs
R: *********************************************************************************
* rudder-agent could not get an updated configuration from the policy server.   *
* This can be caused by a network issue, an unavailable server, or if this      *
* node was deleted from the Rudder root server.                                 *
* Any existing configuration policy will continue to be applied without change. *
*********************************************************************************
R: @@Common@@log_info@@hasPolicyServer-root@@common-root@@00@@common@@StartRun@@2015-01-09 09:00:44+00:00##edb8503c-f3e8-41a2-b811-215ce28cbdf0@#Start execution
R: @@Common@@result_error@@hasPolicyServer-root@@common-root@@00@@Update@@None@@2015-01-09 09:00:44+00:00##edb8503c-f3e8-41a2-b811-215ce28cbdf0@#Cannot update node's policy
R: *********************************************************************************
* rudder-agent could not get an updated configuration from the policy server.   *
* This can be caused by a network issue, an unavailable server, or if this      *
* node was deleted from the Rudder root server.                                 *
* Any existing configuration policy will continue to be applied without change. *
*********************************************************************************
R: @@Common@@result_success@@hasPolicyServer-root@@common-root@@00@@Security parameters@@None@@2015-01-09 09:00:44+00:00##edb8503c-f3e8-41a2-b811-215ce28cbdf0@#The internal environment security is acceptable
R: @@Common@@result_success@@hasPolicyServer-root@@common-root@@00@@Process checking@@None@@2015-01-09 09:00:44+00:00##edb8503c-f3e8-41a2-b811-215ce28cbdf0@#There is an acceptable number of cf-execd processes (between 0 and 2) and cf-agent processes (between 0 and 5)
R: @@Common@@result_success@@hasPolicyServer-root@@common-root@@00@@CRON Daemon@@None@@2015-01-09 09:00:44+00:00##edb8503c-f3e8-41a2-b811-215ce28cbdf0@#The CRON daemon is running
R: @@Common@@result_success@@hasPolicyServer-root@@common-root@@00@@Binaries update@@None@@2015-01-09 09:00:44+00:00##edb8503c-f3e8-41a2-b811-215ce28cbdf0@#The CFengine binaries in /var/rudder/cfengine-community/bin are up to date
R: @@Inventory@@log_info@@inventory-all@@inventory-all@@00@@inventory@@None@@2015-01-09 09:00:44+00:00##edb8503c-f3e8-41a2-b811-215ce28cbdf0@#An inventory was already sent less than 8 hours ago
R: @@Inventory@@result_success@@inventory-all@@inventory-all@@00@@inventory@@None@@2015-01-09 09:00:44+00:00##edb8503c-f3e8-41a2-b811-215ce28cbdf0@#Next inventory scheduled between 00:00 and 06:00
R: @@Common@@log_info@@hasPolicyServer-root@@common-root@@00@@common@@EndRun@@2015-01-09 09:00:44+00:00##edb8503c-f3e8-41a2-b811-215ce28cbdf0@#End execution
R: *********************************************************************************
* rudder-agent could not get an updated configuration from the policy server.   *
* This can be caused by a network issue, an unavailable server, or if this      *
* node has not yet been accepted in the Rudder root server.                     *

for the first run, and the inventory never sent
Happens on Rudder 3.0, may happen on others version


Related issues 1 (0 open1 closed)

Related to Rudder - User story #5918: Have a devault value for policy_server.datReleasedJonathan CLARKE2014-12-04Actions
Actions #1

Updated by Nicolas CHARLES about 9 years ago

Ok, digging into it:
- installing the agent package start the services
- starting the services run the agent
- running the agent runs the inventory

But the policy_server.dat file has never been defined yet, so i don't understand why it tried to sent it

Actions #2

Updated by Nicolas CHARLES about 9 years ago

  • Subject changed from When installing Rudder agent on a debian vagrant box, the agent doesn't send by itself its inventory to When we install rudder-agent package, it tries to send automatically the node inventory to machine "rudder"

The issue is actually that we have a default value for policy_server.dat that contains "rudder"
This value should be ok in most case, but in our office, rudder does exist :)

I guess this is a bit problematic since the first thing the agent does is to send inventory, so having default value may cause issues

Actions #3

Updated by Nicolas CHARLES about 9 years ago

  • Status changed from New to Discussion
  • Assignee set to Benoît PECCATTE
  • Priority changed from 1 to 3
Actions #4

Updated by Benoît PECCATTE about 9 years ago

To keep the default, we could just detect it exists before setting the default.

Actions #5

Updated by Benoît PECCATTE about 9 years ago

  • Assignee changed from Benoît PECCATTE to Nicolas CHARLES

We could just do a "getent hosts rudder" before adding it to the default policy server.

Nico what do you this of this solution ?

Actions #6

Updated by Benoît PECCATTE about 9 years ago

OK, as discussed, we should revert #5918 and have further discussion for 3.1

Actions #7

Updated by Benoît PECCATTE about 9 years ago

  • Status changed from Discussion to In progress
  • Assignee changed from Nicolas CHARLES to Benoît PECCATTE
Actions #8

Updated by Benoît PECCATTE about 9 years ago

  • Status changed from In progress to Discussion
  • Assignee changed from Benoît PECCATTE to Nicolas CHARLES
  • Pull Request set to https://github.com/Normation/rudder-packages/pull/615
Actions #9

Updated by Benoît PECCATTE about 9 years ago

  • Status changed from Discussion to Pending technical review
Actions #10

Updated by Benoît PECCATTE about 9 years ago

  • Pull Request changed from https://github.com/Normation/rudder-packages/pull/615 to https://github.com/Normation/rudder-packages/pull/617
Actions #11

Updated by Benoît PECCATTE about 9 years ago

  • Status changed from Pending technical review to Pending release
  • % Done changed from 0 to 100

Applied in changeset packages:rudder-packages|commit:b753c2f94187e860a46c9347f1fa78331cc39797.

Actions #12

Updated by Nicolas CHARLES about 9 years ago

Applied in changeset packages:rudder-packages|commit:6947ec807a0e4dc70666459ce4637535cc7997a6.

Actions #13

Updated by Vincent MEMBRÉ about 9 years ago

  • Status changed from Pending release to Released

This bug has been fixed in Rudder 3.0.0, which was released on 2015/02/16

Actions

Also available in: Atom PDF