Project

General

Profile

Actions
Copy link

Bug #12026

closed

When a network interface is deleted from a node, it is not removed on the Rudder server

Added by Nicolas CHARLES almost 7 years ago. Updated over 6 years ago.

Status:
Released
Priority:
N/A
Assignee:
Vincent MEMBRÉ
Category:
Web - Nodes & inventories
Target version:
4.1.10
Pull Request:
https://github.com/Normation/ldap-inv...
Severity:
Critical - prevents main use of Rudder | no workaround | data loss | security
UX impact:
User visibility:
Operational - other Techniques | Technique editor | Rudder settings
Effort required:
Small
Priority:
91
Name check:
Fix check:
Regression:

Description

If network interfaces are removed on a node (like, on a docker server), they don't disappear from the Rudder server - resulting in an ever growing list of network interface in Rudder for every nodes

Related issues 3 (0 open — 3 closed)

Related to Rudder - Bug #11912: VM list in a host doesn't match inventory listRejectedActions
Related to Rudder - Bug #12041: No Machine Inventory in nodes list while the details are completeReleasedFrançois ARMANDActions
Has duplicate Rudder - Bug #12539: Upgrading from a SP'ed SLES to a GA keeps the Service Pack fieldRejectedFrançois ARMANDActions
Actions
Copy link
 #1

Updated by François ARMAND almost 7 years ago

  • Related to Bug #11912: VM list in a host doesn't match inventory list added
Actions
Copy link
 #2

Updated by Nicolas CHARLES almost 7 years ago

A workaround can be to delete all network interfaces with following script, then regenerating an inventory

ldapsearch  -o ldif-wrap=no -v -h localhost -p 1389  -x -D "cn=Manager,cn=rudder-configuration" -w secret -b "nodeId=XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX,ou=Nodes,ou=Accepted Inventories,ou=Inventories,cn=rudder-configuration" -s one "(objectClass=networkInterfaceLogicalElement)" 1.1 | grep -e "^dn*" | sed -e "s/dn: //" > dn_to_delete.txt

ldapdelete -h localhost -p 1389 -D "cn=manager,cn=rudder-configuration" -w 'secret' -c -f dn_to_delete.txt

Actions
Copy link
 #3

Updated by François ARMAND almost 7 years ago

  • Status changed from New to In progress
  • Assignee set to François ARMAND
Actions
Copy link
 #4

Updated by François ARMAND almost 7 years ago

  • Severity set to Critical - prevents main use of Rudder | no workaround | data loss | security
  • User visibility set to Operational - other Techniques | Technique editor | Rudder settings
  • Effort required set to Small
  • Priority changed from 0 to 91

So, it happens on any sub-ldap entries of node (i.e mountPoint or networkInterface) or machine (bios, cpu, controllers, etc). So it is critical, because obviously it can impact dyn-group consistancy.

Actions
Copy link
 #5

Updated by François ARMAND almost 7 years ago

  • Status changed from In progress to Pending technical review
  • Assignee changed from François ARMAND to Vincent MEMBRÉ
  • Pull Request set to https://github.com/Normation/ldap-inventory/pull/124
Actions
Copy link
 #6

Updated by François ARMAND almost 7 years ago

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

Updated by François ARMAND almost 7 years ago

  • Related to Bug #12041: No Machine Inventory in nodes list while the details are complete added
Actions
Copy link
 #8

Updated by Vincent MEMBRÉ over 6 years ago

  • Status changed from Pending release to Released

This bug has been fixed in Rudder 4.1.10 and 4.2.4 which were released today.

Actions
Copy link
 #9

Updated by François ARMAND over 6 years ago

  • Has duplicate Bug #12539: Upgrading from a SP'ed SLES to a GA keeps the Service Pack field added
Actions
Copy link

Also available in: Atom PDF