Project

General

Profile

Bug #13803

Network, mask and gateway not correctly parsed from inventory

Added by François ARMAND about 1 month ago. Updated 17 days ago.

Status:
Released
Priority:
N/A
Category:
Web - Nodes & inventories
Target version:
Severity:
Critical - prevents main use of Rudder | no workaround | data loss | security
User visibility:
Getting started - demo | first install | Technique editor and level 1 Techniques
Effort required:
Very Small
Priority:
122

Description

We have an inventory with for ex these values (one interface with one ipv4, one ipv6 address)

<NETWORKS>
     <DESCRIPTION>ens3</DESCRIPTION>
     <DRIVER>virtio_net</DRIVER>
     <IPADDRESS>192.168.180.104</IPADDRESS>
     <IPGATEWAY>192.168.180.1</IPGATEWAY>
     <IPMASK>255.255.255.128</IPMASK>
     <IPSUBNET>192.168.180.0</IPSUBNET>
     <MACADDR>52:54:00:e4:05:47</MACADDR>
     <SPEED>-1</SPEED>
     <STATUS>Up</STATUS>
     <TYPE>ethernet</TYPE>
     <VIRTUALDEV>0</VIRTUALDEV>
   </NETWORKS>
   <NETWORKS>
     <DESCRIPTION>ens3</DESCRIPTION>
     <DRIVER>virtio_net</DRIVER>
     <IPADDRESS6>fe80::5054:ff:fee4:547</IPADDRESS6>
     <IPMASK6>ffff:ffff:ffff:ffff::</IPMASK6>
     <IPSUBNET6>fe80::</IPSUBNET6>
     <MACADDR>52:54:00:e4:05:47</MACADDR>
     <SPEED>-1</SPEED>
     <STATUS>Up</STATUS>
     <TYPE>ethernet</TYPE>
     <VIRTUALDEV>0</VIRTUALDEV>
   </NETWORKS>

Corresponding LDAP content:

dn: networkInterface=ens3,nodeId=xxxxx,ou=Nodes,ou=Accepted Inventories,ou=Inventories,cn=rudder-configuration
networkInterface: ens3
objectClass: networkInterfaceLogicalElement
objectClass: top
networkInterfaceMacAddress: 52:54:00:e4:05:47
status: Up
networkInterfaceType: ethernet
speed: -1
ipHostNumber: fe80::5054:ff:fee4:547
ipHostNumber: 192.168.180.104

The corresponding LDAP entry has no gateway, mask or network.


Subtasks

Bug #13810: Update ldap node entries from ipNetworkNumber => networkSubnetReleasedFrançois ARMAND
Bug #13814: "networkSubnet" is not correctly displayed in search selectReleasedVincent MEMBRÉ

Related issues

Related to Rudder - Bug #13807: Fusion does not parse network gateway correctlyNew

Associated revisions

Revision 07f3f220 (diff)
Added by François ARMAND about 1 month ago

Fixes #13803: Network, mask and gateway not correctly parsed from inventory

History

#1 Updated by François ARMAND about 1 month ago

It only happens when an interface has both ip v4 and up v6 interfaces.

#2 Updated by François ARMAND about 1 month ago

  • Status changed from New to In progress

#3 Updated by François ARMAND about 1 month ago

  • Related to Bug #13807: Fusion does not parse network gateway correctly added

#4 Updated by François ARMAND about 1 month ago

  • Description updated (diff)

So, this is not a small ticket because we need to change our serialisation format, because we need to be able to group [ipHostNumber, networkInterfaceGateway, networkInterfaceMask, ipNetworkNumber] together to be able to tell what ip is linked to what mask.

So, we can't just had gateways/ipnetwork/etc and hope (order is important).

#5 Updated by François ARMAND about 1 month 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/139

#6 Updated by Normation Quality Assistant about 1 month ago

  • Assignee changed from Vincent MEMBRÉ to François ARMAND

#7 Updated by François ARMAND about 1 month ago

  • Status changed from Pending technical review to Pending release

#8 Updated by Vincent MEMBRÉ 17 days ago

  • Status changed from Pending release to Released
This bug has been fixed in Rudder 4.1.17, 4.3.7 and 5.0.3 which were released today.
Changelog
Changelog
Changelog

Also available in: Atom PDF