Bug 1955747
Summary: | minimal ISO doesn't boot on Dell PowerEdge R340 | ||
---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | Nick Carboni <ncarboni> |
Component: | assisted-installer | Assignee: | Nick Carboni <ncarboni> |
assisted-installer sub component: | assisted-service | QA Contact: | Yuri Obshansky <yobshans> |
Status: | CLOSED NOTABUG | Docs Contact: | |
Severity: | unspecified | ||
Priority: | high | CC: | aos-bugs, uschlute |
Version: | 4.8 | ||
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | AI-Team-Core | ||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2021-05-07 13:58:55 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: |
Description
Nick Carboni
2021-04-30 18:04:26 UTC
Problem also occurs with one ironic provided ISO, but things work properly when changing the ISO_IMAGE_TYPE to full-iso in the assisted-service. Can you give some more details on the (In reply to Ulrich Schlueter from comment #2) > Problem also occurs with one ironic provided ISO, but things work properly > when changing the ISO_IMAGE_TYPE to full-iso in the assisted-service. Can you give some more details about the "ironic provided ISO"? How was it created? Is that something we can get access to? Looks like this was server related after all. The server showed additional (corrupted) entries in the UEFI boot sequence that most likely confused the boot process (trying to boot from a non-existing virtual CD, not the one shown in the UI) . Removing these entries help with the ironic case. Next step retesting with the minimal-iso Re-testing with the minimal ISO worked. So the corruption in the boot sequence seems to have caused the observed symptoms. Unexplained things: 1) why the boot process worked with the full iso. 2) what created the rogue entries. Anyway, from my perspective this BZ can be closed. Closing this as it was due to UEFI configuration issues on the host. |