Project

General

Profile

Actions
Copy link

Bug #3887

closed

Error when adding and deleting a node several times

Added by François ARMAND over 10 years ago. Updated about 9 years ago.

Status:
Released
Priority:
3
Assignee:
Nicolas CHARLES
Category:
Web - Nodes & inventories
Target version:
2.6.4
Pull Request:
https://github.com/Normation/rudder/p...
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:

Description

When adding a node, then deleting it, then adding it back, we can't delete it anymore due to that error:

Node with id a60bdb08-2669-4cd5-86a4-c5f77c1ded14 was not found
Error message was: could not get machine from container 
machineId=422EE2BE-1314-117B-2FB3-54ADF3F2CD5B,ou=Machines,ou=Removed Inventories,ou=Inventories,cn=rudder-configuration : 
Failure(DN machineId=422EE2BE-1314-117B-2FB3-54ADF3F2CD5B,
  ou=Machines,ou=Removed Inventories,ou=Inventories,cn=rudder-configuration 
does not belong to machine inventories DN 
  ou=Machines,ou=Accepted Inventories,ou=Inventories,cn=rudder-configuration

Related issues 1 (0 open — 1 closed)

Related to Rudder - Bug #3892: Machine in deleted branch does not correclty move back to accepted for new nodesRejectedFrançois ARMAND2013-08-29Actions
Actions
Copy link
 #1

Updated by François ARMAND over 10 years ago

There seems to be two bug here:

  • we should not have an error for a machine that is not in "accepted"
  • we should "move back" machine from deleted to accepted when accepting a node with the same machine as a previously deleted one

The second one is more involving than the first, I'm opening a second ticket for it: #3892

Actions
Copy link
 #2

Updated by François ARMAND over 10 years ago

  • Status changed from 8 to Pending technical review
  • Assignee changed from François ARMAND to Nicolas CHARLES
  • Target version changed from 2.4.8 to 2.6.4
  • Pull Request set to https://github.com/Normation/rudder/pull/307

Actually, it was due to the addition of the machine type (physical, virtual, etc) in the node summary.

PR: https://github.com/Normation/rudder/pull/307

Actions
Copy link
 #3

Updated by François ARMAND over 10 years ago

  • Status changed from Pending technical review to Pending release
  • % Done changed from 0 to 100
Actions
Copy link
 #5

Updated by François ARMAND over 10 years ago

  • Status changed from Pending release to In progress
  • Pull Request deleted (https://github.com/Normation/rudder/pull/307)

It seems that something remains in the LDAPSearch, for 2.6 and up. When searching, we still see the bug: I revert the previous (incorrect) correct, and will submit an other pull request.

Actions
Copy link
 #6

Updated by François ARMAND over 10 years ago

  • Assignee changed from Nicolas CHARLES to François ARMAND
Actions
Copy link
 #7

Updated by François ARMAND over 10 years ago

  • Status changed from In progress to Pending technical review
  • Assignee changed from François ARMAND to Nicolas CHARLES
  • Pull Request set to https://github.com/Normation/rudder/pull/310
Actions
Copy link
 #8

Updated by François ARMAND over 10 years ago

  • Status changed from Pending technical review to Pending release
Actions
Copy link
 #10

Updated by Nicolas PERRON over 10 years ago

  • Status changed from Pending release to Released

This bug has been fixed in Rudder 2.6.4, which was released today.
Check out:

Actions
Copy link
 #11

Updated by Benoît PECCATTE about 9 years ago

  • Category changed from 26 to Web - Nodes & inventories
Actions
Copy link

Also available in: Atom PDF