Actions
Bug #16074
closed
When deleting completely a rudder-agent, it is very hard to re-install a functionnal agent on it
Pull Request:
Severity:
Major - prevents use of part of Rudder | no simple workaround
UX impact:
User visibility:
Operational - other Techniques | Rudder settings | Plugins
Effort required:
Very Small
Priority:
80
Name check:
Fix check:
To do
Regression:
Description
If you uninstall rudder-agent from a node, and then remove the ppkeys of it from the node, it will be hard to make the agent come back in the Rudder server.
--> the webapp will throw errors like:
[2019-10-29 09:04:48] ERROR inventory-processing - Rejecting Inventory 'agent1-96d90e95-54ee-4d20-a95e-2d6dc4dccf61.ocs' for Node '96d90e95-54ee-4d20-a95e-2d6dc4dccf61' because the Inventory signature is not valid: the Inventory was not signed with the same agent key as the one saved within Rudder for that Node. If you updated the agent key on this node, you can update the key stored within Rudder with the following command on the Rudder Server: '/opt/rudder/bin/rudder-keys change-key 96d90e95-54ee-4d20-a95e-2d6dc4dccf61 <your new public key>'. If you did not change the key, please ensure that the node sending that inventory is actually the node registered within Rudder
Thing is, rudder-keys does not seem to work if we already removed the agent from the webapp...
Updated by 
Updated by 
Updated by
Actions