-
Bug
-
Resolution: Done-Errata
-
Major
-
4.10
-
Important
-
None
-
5
-
Metal Platform 236, Metal Platform 239, Metal Platform 240, Metal Platform 241, Metal Platform 242, Metal Platform 243, Metal Platform 245, Metal Platform 246
-
8
-
Unspecified
-
-
Release Note
-
-
9/13: u/s patch finalized & under review
Description of problem:
If secure boot is currently disabled, and user attempts to enable it via ZTP, install will not begin the first time ZTP was triggered.
When secure boot is enabled viz ZTP, then boot options will be configured before virtual CD was attached, thus first boot will be booting into existing HD with secure boot on. Install will then get stuck because boot from CD was never triggered.
Version-Release number of selected component (if applicable):
4.10
How reproducible:
Always
Steps to Reproduce:
1. Secure boot is currently disabled in bios
2. Attempt to deploy a cluster with secure boot enabled via ZTP
3.
Actual results:
- spoke cluster got booted with secure boot option toggled, into existing HD
- spoke cluster did not boot into virtual CD, thus install never started.
- agentclusterinstall gets stuck here:
State: insufficient
State Info: Cluster is not ready for install
Expected results:
- installation started and completed successfully
Additional info:
Secure boot config used in ZTP siteconfig:
http://registry.kni-qe-0.lab.eng.rdu2.redhat.com:3000/kni-qe/ztp-site-configs/src/ff814164cdcd355ed980f1edf269dbc2afbe09aa/siteconfig/master-2.yaml#L40
- is cloned by
-
OCPBUGS-19884 [4.14] Install does not begin if secure boot was enabled for the first time
- Closed
- is depended on by
-
OCPBUGS-19884 [4.14] Install does not begin if secure boot was enabled for the first time
- Closed
- is duplicated by
-
OCPBUGS-8434 Secure boot - bmh provisioning error with secure boot enabled
- Closed
- links to
-
RHSA-2023:7198 OpenShift Container Platform 4.15 security update