Bug 1830161
| Summary: | No network devices shows up when PXE booting via UEFI + IPv4 | |||
|---|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | rlopez | |
| Component: | Bare Metal Hardware Provisioning | Assignee: | Julia Kreger <jkreger> | |
| Bare Metal Hardware Provisioning sub component: | ironic | QA Contact: | Amit Ugol <augol> | |
| Status: | CLOSED ERRATA | Docs Contact: | ||
| Severity: | medium | |||
| Priority: | high | CC: | jkreger, mburke, rbartal, stbenjam, william.caban, yprokule | |
| Version: | 4.4 | Keywords: | Triaged | |
| Target Milestone: | --- | |||
| Target Release: | 4.5.0 | |||
| Hardware: | Unspecified | |||
| OS: | Unspecified | |||
| Whiteboard: | ||||
| Fixed In Version: | Doc Type: | Bug Fix | ||
| Doc Text: |
Cause:
A iPXE UEFI loader binary was in for IPv4 network boot operations that was designed to utilize network drivers supplied with iPXE.
Consequence:
This results in a "No network found" error as a result on the console of the machine being deployed.
Fix:
UEFI firmware environments include a basic networking stack which can be utilized by the iPXE loader. As a result, the iPXE "snponly.efi" binary shall be used instead to perform the initalization of iPXE as the underlying UEFI network stack can be utilized.
Result:
Deployments of UEFI machines utilizing IPv4 and iPXE should now succeed.
|
Story Points: | --- | |
| Clone Of: | ||||
| : | 1830298 (view as bug list) | Environment: | ||
| Last Closed: | 2020-07-13 17:34:07 UTC | Type: | Bug | |
| Regression: | --- | Mount Type: | --- | |
| Documentation: | --- | CRM: | ||
| Verified Versions: | Category: | --- | ||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | ||
| Cloudforms Team: | --- | Target Upstream Version: | ||
| Embargoed: | ||||
| Bug Depends On: | ||||
| Bug Blocks: | 1830298 | |||
|
Description
rlopez
2020-05-01 00:01:26 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 Julia -- I am an OpenShift technical writer trying to write a release note for this fixed issue. However, I have little experience and understanding of this realm. Can I bother you to take a look at what I draft and let me know if I'm even close? We use the Cause-Consequence-Fix-Result format for reporting fixed issues. Thank you in advance for any help. Michael Because the UEFI boot process was using the `ipxe.efi` binary, if using IPv4 networks, the boot process reported that there are no networks are found. As a result, the Preboot eXecution Environment (PXE) boots the masters with no network devices. The dnsmasq.conf file has been updated to use the `snponly.efi` binary. The PXE boots with the correct network drivers and the master have network connectivity. So, your note is a bit confusing, lets try: Because the UEFI boot process was using the `ipxe.efi` binary when using IPv4 networks, the boot process reported that there were no network devices found. As a result, the Preboot eXecution Environment (PXE) boots the machines with "No network devices". The dnsmasq.conf file has been updated to use the `snponly.efi` binary for IPv4 networks. The machines booting with PXE utilize the UEFI network drivers and are able to deploy as they have network connectivity. It glosses over technical details of the differences between iPXE generalized PXE, but it should still work. 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:2409 |