Project

General

Profile

Actions

Bug #14707

closed

Impossible to recreate a node deleted

Added by P C about 5 years ago. Updated over 4 years ago.

Status:
Rejected
Priority:
N/A
Category:
Web - Nodes & inventories
Target version:
Severity:
Major - prevents use of part of Rudder | no simple workaround
UX impact:
User visibility:
Operational - other Techniques | Rudder settings | Plugins
Effort required:
Priority:
48
Name check:
Fix check:
Regression:

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)
2)
buttons (scripts) : Delete , Undelete, Destroy
- adapt script : rudder-keys
3) ...
and update the doc :
- How to delete a node?
- How to recreate/undelete" a node


Related issues 3 (0 open3 closed)

Related to Rudder - Bug #9609: Deleted node should be periodically fully erased in LDAP (after some ttl)ReleasedNicolas CHARLESActions
Related to Rudder - Bug #13843: Inventory keeps its key certified when node is deleted even is keystatus is erasedReleasedFrançois ARMANDActions
Is duplicate of Rudder - Bug #14209: Impossible to reset the status of a Node using rudder-keys cliReleasedVincent MEMBRÉActions
Actions

Also available in: Atom PDF