Project

General

Profile

Actions

Bug #3669

closed

Rudder ignores IP aliases on network interfaces

Added by Matthieu CERDA almost 11 years ago. Updated about 9 years ago.

Status:
Released
Priority:
3
Category:
Web - Nodes & inventories
Target version:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:

Description

Rudder seems to ignore IP aliases on network interfaces, and only takes the first occurrence of a given interface in a fusion inventory file.

Example:

    <NETWORKS>
      <DESCRIPTION>eth0</DESCRIPTION>
      <DRIVER>virtio_net</DRIVER>
      <IPADDRESS>192.168.110.50</IPADDRESS>
      <IPMASK>255.255.255.0</IPMASK>
      <IPSUBNET>192.168.110.0</IPSUBNET>
      <MACADDR>52:54:00:56:1e:96</MACADDR>
      <SLAVES></SLAVES>
      <STATUS>Up</STATUS>
    </NETWORKS>
    <NETWORKS>
      <DESCRIPTION>eth0</DESCRIPTION>
      <DRIVER>virtio_net</DRIVER>
      <IPADDRESS>192.168.110.250</IPADDRESS>
      <IPMASK>255.255.255.0</IPMASK>
      <IPSUBNET>192.168.110.0</IPSUBNET>
      <MACADDR>52:54:00:56:1e:96</MACADDR>
      <SLAVES></SLAVES>
      <STATUS>Up</STATUS>
    </NETWORKS>

The report containing this snippet is accepted on a 2.4 Rudder, but only the first IP is used in the interface. It also seems that this is the reason Rudder never displays IPv6 addresses.

Actions

Also available in: Atom PDF