Bug #14707
closed
Impossible to recreate a node deleted
Description
If you delete a node :
server : Delete button on the Nodes manager view
client : apt-get purge --auto-remove rudder-agent & rm -fR .../rudder
and the recreate it : apt-get install rudder-agent
the 'new' node will never arrive in the view "Accept new nodes"
Explanation : the node is not really deleted, it is still present, with its previous public key, in the ldap db on "Removed Inventories" and no more on "Active Inventories". Why?
Quick solution : duplicate the script rudder-keys in rudder-keys2 and change line 38 :
#01 ACCEPTED_NODES_BASE="ou=Nodes,ou=Accepted Inventories,ou=Inventories,cn=rudder-configuration"
ACCEPTED_NODES_BASE="ou=Nodes,ou=Removed Inventories,ou=Inventories,cn=rudder-configuration" #01
Proposed solutions :
1) buttun Delete > Destroy (no more data in the ldap db) buttons (scripts) : Delete , Undelete, Destroy
2)
- adapt script : rudder-keys
3) ...
and update the doc :
- How to delete a node?
- How to recreate/undelete" a node
Updated by Alexis Mousset over 5 years ago
- Related to Bug #9609: Deleted node should be periodically fully erased in LDAP (after some ttl) added
Updated by François ARMAND over 5 years ago
- User visibility set to Operational - other Techniques | Rudder settings | Plugins
- Priority changed from 0 to 52
What ou experience is not what is expected. A deleted node from the UI should come back in "pending", and the fact that its UUID changed or that it goes to "deleted" should have nothing to do with that.
Perhaps you hit a variant of that bug: https://issues.rudder.io/issues/13843
We will investigate.
Updated by François ARMAND over 5 years ago
- Related to Bug #13843: Inventory keeps its key certified when node is deleted even is keystatus is erased added
Updated by François ARMAND over 5 years ago
- Translation missing: en.field_tag_list set to community
- Assignee set to François ARMAND
- Target version set to 5.0.10
Updated by François ARMAND over 5 years ago
- Related to Bug #14209: Impossible to reset the status of a Node using rudder-keys cli added
Updated by Vincent MEMBRÉ over 5 years ago
- Target version changed from 5.0.10 to 5.0.11
Updated by Vincent MEMBRÉ over 5 years ago
- Target version changed from 5.0.11 to 5.0.12
Updated by Vincent MEMBRÉ over 5 years ago
- Target version changed from 5.0.12 to 5.0.13
- Priority changed from 52 to 50
Updated by Vincent MEMBRÉ about 5 years ago
- Target version changed from 5.0.13 to 5.0.14
- Priority changed from 50 to 49
Updated by François ARMAND about 5 years ago
- Priority changed from 49 to 48
Tested, still the case in 5.0.14.
This is especially strange, since the node is deleted and we have keyStatus=undefined in node inventory.
Updated by François ARMAND about 5 years ago
- Status changed from New to Rejected
This was actually a duplicate of #14202. I'm closing this one.
Updated by François ARMAND about 5 years ago
- Related to deleted (Bug #14209: Impossible to reset the status of a Node using rudder-keys cli)
Updated by François ARMAND about 5 years ago
- Is duplicate of Bug #14209: Impossible to reset the status of a Node using rudder-keys cli added