Actions
Bug #13803
closedNetwork, mask and gateway not correctly parsed from inventory
Bug #13803:
Network, mask and gateway not correctly parsed from inventory
Status:
Released
Priority:
N/A
Assignee:
Category:
Web - Nodes & inventories
Target version:
Pull Request:
Severity:
Critical - prevents main use of Rudder | no workaround | data loss | security
UX impact:
User visibility:
Getting started - demo | first install | Technique editor and level 1 Techniques
Effort required:
Very Small
Priority:
122
Name check:
Fix check:
Regression:
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.
Updated by François ARMAND about 7 years ago
It only happens when an interface has both ip v4 and up v6 interfaces.
Updated by François ARMAND about 7 years ago
- Status changed from New to In progress
Updated by François ARMAND about 7 years ago
- Related to Bug #13807: Fusion does not parse network gateway correctly added
Updated by François ARMAND about 7 years 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).
Updated by François ARMAND about 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/139
Updated by Rudder Quality Assistant about 7 years ago
- Assignee changed from Vincent MEMBRÉ to François ARMAND
Updated by François ARMAND about 7 years ago
- Status changed from Pending technical review to Pending release
Applied in changeset ldap-inventory|07f3f220c9151663b35b1f3ef8f7797c9c358d63.
Updated by Vincent MEMBRÉ about 7 years ago
Actions