Hi Guys,
I am working on the foreman 2.3.1 and trying to configure the Auto discovery plugin where i am getting below error while boot
Any clue why this error is occurring.
What network interface ids does this server have? Can you list them?
Don’t it match against the NIC filter mentioned?
Hi Izap,
on the discovered server dont know but on foreman server below are the details
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group defaul t qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: ens192: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group de fault qlen 1000
link/ether 00:50:56:ba:ef:c3 brd ff:ff:ff:ff:ff:ff
inet 10.10.10.188/24 brd 10.10.10.255 scope global noprefixroute ens192
valid_lft forever preferred_lft forever
inet 10.10.10.86/24 scope global secondary ens192
valid_lft forever preferred_lft forever
inet6 fe80::250:56ff:feba:efc3/64 scope link
valid_lft forever preferred_lft forever
3: ens224: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group de fault qlen 1000
link/ether 00:50:56:ba:a9:34 brd ff:ff:ff:ff:ff:ff
inet 192.168.101.7/23 brd 192.168.101.255 scope global noprefixroute ens224
valid_lft forever preferred_lft forever
inet6 fe80::250:56ff:feba:a934/64 scope link
valid_lft forever preferred_lft forever
To check I change the FDI 3.7 to 3.5 where it works on the same setting.In 3.5 does it require any other setting which need enable in foreman.
Thanks
Identifiers look good. There must be something wrong with the network configuration, on the screenshot IP addresses are both marked as not available. There should be at least one since there is a response from server. Investigate, provide more logs.