Rudder

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