Project

General

Profile

Actions

Bug #16851

closed

Deleted node can't be added again

Added by Jean Cardona about 4 years ago. Updated 11 months ago.

Status:
Resolved
Priority:
N/A
Assignee:
-
Category:
Web - Nodes & inventories
Target version:
-
Severity:
Minor - inconvenience | misleading | easy workaround
UX impact:
User visibility:
Operational - other Techniques | Rudder settings | Plugins
Effort required:
Priority:
0
Name check:
To do
Fix check:
To do
Regression:
No

Description

When adding a node, rudder checks deleted nodes and does not allow adding a node that matches deleted nodes.

Actions #1

Updated by Nicolas CHARLES about 4 years ago

Ha, a user on gitter reporting that doing

rudder agent stop
rm /var/backups/rudder/uuid* 
rm /var/backups/rudder/uuid* 
rm /var/backups/rudder/* 
/opt/rudder/bin/rudder-uuidgen >  /opt/rudder/etc/uuid.hive
rudder agent factory-reset

solved the issue
can you check ?

Actions #2

Updated by Jean Cardona about 4 years ago

Nicolas CHARLES wrote in #note-1:

Ha, a user on gitter reporting that doing
[...]
solved the issue
can you check ?

Yes, the issue seems fixed for that host. Just waiting for the report to be deleted didn't seem to change anything.

Actions #3

Updated by Alexis Mousset almost 4 years ago

  • Category set to Web - Nodes & inventories
Actions #4

Updated by François ARMAND over 3 years ago

  • Subject changed from issue when adding node to Deleted node can't be added again
  • Severity changed from Major - prevents use of part of Rudder | no simple workaround to Minor - inconvenience | misleading | easy workaround
  • User visibility set to Operational - other Techniques | Rudder settings | Plugins
  • Priority changed from 0 to 31

I think it was corrected at some point, but it need to be checked.

Actions #5

Updated by François ARMAND 11 months ago

  • Status changed from New to Resolved
  • Priority changed from 31 to 0
  • Regression set to No

I was confirmed to work on 7.x

Actions

Also available in: Atom PDF