Bug 1972213
Summary: | Openshift Installer| UEFI mode | BM hosts have BIOS halted | |||
---|---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | Bob Fournier <bfournie> | |
Component: | Bare Metal Hardware Provisioning | Assignee: | Bob Fournier <bfournie> | |
Bare Metal Hardware Provisioning sub component: | ironic | QA Contact: | Lubov <lshilin> | |
Status: | CLOSED ERRATA | Docs Contact: | ||
Severity: | urgent | |||
Priority: | urgent | CC: | amccrae, augol, bdonahue, bfournie, bgilbert, bootloader-eng-team, derekh, dgilmore, dhellmann, djuran, dtantsur, fmartine, grajaiya, gvincent, jfrye, jkreger, jpoulin, kiran, lshilin, lszubowi, mgourin, miabbott, nkononov, peterm, pjones, racedoro, sbaker, sdodson, tsedovic, walters, yjoseph, ykashtan | |
Version: | 4.8 | Keywords: | AutomationBlocker, TestBlocker, Triaged | |
Target Milestone: | --- | |||
Target Release: | 4.8.0 | |||
Hardware: | x86_64 | |||
OS: | Linux | |||
Whiteboard: | ||||
Fixed In Version: | Doc Type: | Bug Fix | ||
Doc Text: |
RN content:
Previously, in UEFI mode, the ironic-python-agent created a UEFI bootloader entry after downloading the RHCOS image. When using an RHCOS image based on RHEL 8.4, the image could fail to boot using this entry, depending on the ordering of UEFI entries. If the entry installed by Ironic was used when booting the image, the boot could fail and output a BIOS error screen. This is fixed by the ironic-python-agent configuring the boot entry based on a CSV file located in the image, instead of using a fixed boot entry. The image boots properly without error.
-----
Cause: In UEFI mode, after downloading the RHCOS image, the ironic-python-agent creates a UEFI bootloader entry. When using an RHCOS image based on RHEL 8.4, the image may fail to boot using this entry.
Consequence: Depending on the ordering of UEFI entries, if the entry installed by Ironic is used when booting the image the boot may fail and output a BIOS error screen.
Fix: The ironic-python-agent will configure the boot entry based on a CSV file located in the image instead of using a fixed boot entry.
Result: The image boots properly without an error.
|
Story Points: | --- | |
Clone Of: | 1966129 | |||
: | 1973314 (view as bug list) | Environment: | ||
Last Closed: | 2021-07-27 23:12:54 UTC | Type: | --- | |
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: | 1966129, 1976074 | |||
Bug Blocks: | 1970632, 1971018, 1973314, 1976079, 2013591 |
Comment 2
Lubov
2021-06-21 08:37:53 UTC
run on 4.8.0-0-rc.0 2 deployments - no red screen. BM servers DELL R740 Should be same release note as https://bugzilla.redhat.com/show_bug.cgi?id=1966129 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 (Moderate: OpenShift Container Platform 4.8.2 bug fix and security update), 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/RHSA-2021:2438 |