-
Bug
-
Resolution: Unresolved
-
Undefined
-
None
-
4.15, 4.16
-
Important
-
No
-
Rejected
-
False
-
oDescription of problem:
As described in https://github.com/openshift/installer/pull/7484#issuecomment-1833285723, when nodes boot via UEFI and the agent-installer performs an OKD/FCOS installation, the default uefi entry is created and set as default, but it targets [EFI]/redhat/shim* instead of [EFI]/fedora/shim*.
This might be due to https://github.com/openshift/assisted-installer/blob/master/src/ops/ops.go#L251-L261
Version-Release number of selected component (if applicable):
4.15 OKD (on FCOS and SCOS), 4.16 OCP (when not using RHCOS, but SCOS),
How reproducible:
Always
Steps to Reproduce:
1. Configure nodes to boot via UEFI
2. Install okd through the agent installation (or OCP when the machine-os-content is not rhel, but CentOS steam CoreOS)
3.
Actual results:
The default boot entry loads the first-stage bootloader from [EFI]/redhat/shimx64.efi
Expected results:
The default boot entry loads the first-stage bootloader from [EFI]/(fedora|centos)/shimx64.efi when FCOS (or SCOS) is the base os
Additional info:
- is duplicated by
-
-
- Closed
-
- relates to
-
AGENT-367 OKD FCOS Support
-
- Closed
-