+++ This bug was initially created as a clone of Bug #1830161 +++ Description of problem: When booting via UEFI, using IPv4 PXE protocol, error of no network devices shows up. Via https://github.com/openshift/ironic-image/blob/master/dnsmasq.conf.j2#L28 we see that ipxe.efi is set but it should be using snponly.efi https://github.com/metal3-io/ironic-image/blob/master/dnsmasq.conf.j2#L41 Steps to Reproduce: 1. Ensure UEFI+ IPv4 PXE protocol in UEFI settings 2. Attempt an IPI on BM install Actual results: Fails to PXE masters with No network devices Expected results: Properly PXE the master nodes. https://github.com/openshift/ironic-image/blob/master/dnsmasq.conf.j2#L28 https://github.com/metal3-io/ironic-image/blob/master/dnsmasq.conf.j2#L41 --- Additional comment from Julia Kreger on 2020-05-01 00:13:14 UTC --- UEFI stacks are supposed to supply network stacks to the firmware images loaded such as those for ipxe before the operating system loads. This means we should be using the snponly.efi binary for uefi with IPv4. With IPv6, the file is already correct. Pull requests created for openshift and metal3. https://github.com/openshift/ironic-image/pull/76 https://github.com/metal3-io/ironic-image/pull/152
*** Bug 1835984 has been marked as a duplicate of this bug. ***
Created attachment 1691126 [details] pxe_efi.png We can see that snponly.efi is loaded on IPv4 provisioning network with 4.4.5 image.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2020:2180