Plugins » Discovery

The newest FDI image version 3.7.3 is somehow acting differently collecting networking facts:

[root@fdi ~]# FACTERLIB=/usr/share/fdi/facts tfm-ruby /opt/theforeman/tfm/root/usr/bin/facter networking
{
  dhcp => "10.2.0.104",
  fqdn => "fdi.",
  hostname => "fdi",
  interfaces => {
    eno1 => {
      bindings => [
        {
          address => "10.2.240.156",
          netmask => "255.255.0.0",
          network => "10.2.0.0" 
        }
      ],
      bindings6 => [
        {
          address => "fe80::4adf:37ff:fe7f:3fb8",
          netmask => "ffff:ffff:ffff:ffff::",
          network => "fe80::" 
        }
      ],
      dhcp => "10.2.0.104",
      ip => "10.2.240.156",
      ip6 => "fe80::4adf:37ff:fe7f:3fb8",
      mac => "48:df:XX:XX:XX:XX",
      mtu => 1500,
      netmask => "255.255.0.0",
      netmask6 => "ffff:ffff:ffff:ffff::",
      network => "10.2.0.0",
      network6 => "fe80::",
      scope6 => "link" 
    },
    lo => {
      bindings => [
        {
          address => "127.0.0.1",
          netmask => "255.0.0.0",
          network => "127.0.0.0" 
        }
      ],
      bindings6 => [
        {
          address => "::1",
          netmask => "ffff:ffff:ffff:ffff:ffff:ffff:ffff:ffff",
          network => "::1" 
        }
      ],
      ip => "127.0.0.1",
      ip6 => "::1",
      mtu => 65536,
      netmask => "255.0.0.0",
      netmask6 => "ffff:ffff:ffff:ffff:ffff:ffff:ffff:ffff",
      network => "127.0.0.0",
      network6 => "::1",
      scope6 => "host" 
    }
  },
  ip => "10.2.240.156",
  ip6 => "fe80::4adf:37ff:fe7f:3fb8",
  mac => "48:df:XX:XX:XX:XX",
  mtu => 1500,
  netmask => "255.255.0.0",
  netmask6 => "ffff:ffff:ffff:ffff::",
  network => "10.2.0.0",
  network6 => "fe80::",
  primary => "eno1",
  scope6 => "link" 
}

on this machine i have 2 x 10 Gbit/s interfaces that i can also see in the fdi:

[root@fdi ~]# ifconfig
eno1: flags=4419<UP,BROADCAST,RUNNING,PROMISC,MULTICAST>  mtu 1500
        inet 10.2.240.156  netmask 255.255.0.0  broadcast 10.2.255.255
        inet6 fe80::4adf:37ff:fe7f:3fb8  prefixlen 64  scopeid 0x20<link>
        ether 48:df:37:7f:3f:b8  txqueuelen 1000  (Ethernet)
        RX packets 30836  bytes 16855273 (16.0 MiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 30235  bytes 1438550 (1.3 MiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

eno2: flags=4419<UP,BROADCAST,RUNNING,PROMISC,MULTICAST>  mtu 1500
        ether 48:df:37:7f:3f:b9  txqueuelen 1000  (Ethernet)
        RX packets 12  bytes 2580 (2.5 KiB)
        RX errors 0  dropped 2  overruns 0  frame 0
        TX packets 19  bytes 1387 (1.3 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

lo: flags=329<UP,LOOPBACK,RUNNING,PROMISC>  mtu 65536
        inet 127.0.0.1  netmask 255.0.0.0
        inet6 ::1  prefixlen 128  scopeid 0x10<host>
        loop  txqueuelen 1000  (Local Loopback)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

The only difference between eno1 and eno2 seems to be that eno2 does not have any ip configuration. This should be working as 1 interfaces for provisioning in Foreman is enough. Due to the missing interface fact i am not able to deploy bonding devices.