Project

General

Profile

Bug #31826

Discovered nodes without default route cannot be processed

Added by Lukas Zapletal over 1 year ago. Updated about 1 year ago.

Status:
New
Priority:
Low
Category:
-
Target version:
Difficulty:
Triaged:
Yes
Bugzilla link:
Pull request:
Fixed in Releases:
Found in Releases:

Description

Discovered nodes without default route do not get "networking->ip" and "networking->ip6" and "networking->primary" facts, therefore detection of the primary interface fails in core, thus discovery is unable to continue.

2021-02-05T16:40:58 [D|app|7ce03c4a] We have following interfaces 'ens192' based on facts
2021-02-05T16:40:58 [D|app|7ce03c4a] Interface ens192 facts: {"bindings"=>[{"address"=>"10.28.236.10", "netmask"=>"255.255.255.0", "network"=>"10.28.236.0"}], "bindings6"=>[{"address"=>"fe80::250:56ff:feac:18b6", "netmask"=>"ffff:ffff:ffff:ffff::", "network"=>"fe80::"}], "dhcp"=>"10.28.236.3", "macaddress"=>"00:50:56:ac:18:b6", "mtu"=>1500, "scope6"=>"link"}
2021-02-05T16:40:58 [D|app|7ce03c4a] Discovery fact parser detected primary interface: 
2021-02-05T16:40:58 [W|app|7ce03c4a] Host discovery failed, facts: {} error (Foreman::Exception): ERF42-9680 [Foreman::Exception]: Unable to find primary NIC with 52:d0:8d:34:12:84 specified via 'discovery_bootif', NIC filter: ["lo", "en*v*", "usb*", "vnet*", "macvtap*", ";vdsmdummy;", "veth*", "docker*", "tap*", "qbr*", "qvb*", "qvo*", "qr-*", "qg-*", "vlinuxbr*", "vovsbr*", "br-int"]

This needs to be fixed so both facter 2 and 3 do work (with and without default route).


Related issues

Related to Discovery - Bug #31943: Facter 4.x does not report uninitialized interfacesResolved

History

#1 Updated by Lukas Zapletal over 1 year ago

  • Priority changed from Urgent to High
  • Description updated (diff)
  • Subject changed from Discovery is broken - unable to detect primary interface to Discovered nodes without default route cannot be processed

#2 Updated by Lukas Zapletal about 1 year ago

  • Related to Bug #31943: Facter 4.x does not report uninitialized interfaces added

#3 Updated by Lukas Zapletal about 1 year ago

This should be retested after #31943 is fixed.

#4 Updated by Lukas Zapletal about 1 year ago

  • Priority changed from High to Low

I believe this was resolved with the associated issue.

Also available in: Atom PDF