Using Foreman 1.24.2 (and an external DHCP server) when booting a machine using Foreman Discovery Image (3.5.7) the automatic network configuration that starts with a countdown fails to obtain a network configuration from DHCP. Upon failing, the message in the logs show two network devices, 1: lo: 127.0.0.1 and 2: ens192 which doesn’t obtain an IP.
- DHCP LEASES *
cat: /var/lib/NetworkManager/dhclient-*.lease: No such file or directory
- DNS *
cat: /etc/resolv.conf: No such file or directory
However, if I interrupt the automatic network configuration countdown (pressing any key), then choose to
Discover with DHCP, select the only NIC option available (ens192), then the network is configured correctly and confirming the following screens about foreman server location etc all works and the facts are published to the foreman server. My understanding is that this is exactly what should be happening during the countdown stage anyway so I’m not sure what the difference is here - perhaps a race condition but extending the timeout doesn’t help…
Using (what I believe are) exactly the same settings on an existing Foreman 1.23.1 server (FDI 3.5.1) yields different results and automatic network configuration of the FDI image works first time without any manual intervention. I have tried copying the 3.5.1 FDI image to the 1.24.2 foreman server just in case and still no joy with that either.
Network configuration for DHCP shouldn’t require any manual intervention and the initial network configuration should work automatically.
Foreman and Proxy versions:
Foreman and Proxy plugin versions:
Distribution and version:
CentOS 7 and Ubuntu 18.04
Other relevant data:
Using OOTB templates, no changes here.