Rudder

Several issues here that are really counter intuitive for the user.
When a node fails to run its first inventory in the postinst, it will stay in the bootstrap policies, which requires to run 'rudder agent update' to be run.
But then, if the node communicates with its policy server, send its first successful inventory, but we do not accept it, the command 'rudder agent update' will fail with the following:

root@agent1:~# rudder agent update
   error: Can't stat file '/var/rudder/share/f49b0730-d428-4289-a0f7-de18c2ce2235/rules/cfengine-community/rudder-promises-generated' on '192.168.25.4' in files.copy_from promise, it may be missing or access may not be authorized
   error: Errors encountered when actuating files promise '/var/rudder/cfengine-community/inputs/rudder-promises-generated.tmp'
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: Rudder agent policies could not be updated.

This behavior is pretty misleading as the same command gives different expected results depending on how far we are in the accepting process. I feel like we should have a dedicated command for the specific bootstrap update which should be repeatable.