-
Notifications
You must be signed in to change notification settings - Fork 294
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
OKD on SCOS (4.14 2024-01-30) deployment fails on vSphere UPI, SCOS bad shim signature #1938
Comments
Be sure you are not using secure boot for the guest machine. Under Settings, click the VM Options tab, and expand Boot Options. I am using Bios for firmware, which has worked in the past. If you are using EFI firmware, be sure to deselect the Secure Boot check box. |
Broken Secure Boot on SCOS is a known issue: https://issues.redhat.com/browse/RHEL-4391 |
Yes, disabling secure boot as a workaround solved the problem. I could successfully deploy such an OKD/SCOS cluster. |
If someone is looking for a workaround when installing on vSphere UPI ... I wrote our automation in PowerShell to be able to use PowerCLI for VMware vSphere tasks. What I did there to disable Secure Boot:
|
I've grabbed your tip and will put it in the release notes. Closing this for completeness. |
BTW, FCOS 40 also has this "bad shim signature" problem now. |
@kai-uwe-rommel openshift/installer#8793 But probably only will be backported to 4.16 edit: (oops I misread this was upi, the change above was for ipi) |
Describe the bug
Tried to deploy a okd-scos-2024-01-30-032525 cluster on vSphere UPI.
After pulling the SCOS image onto the bootstrap VM with FCOS, the reboot fails with "bad shim signature"
Version
okd-scos-2024-01-30-032525
on vSphere UPI
How reproducible
100%
Log bundle
![grafik](https://private-user-images.githubusercontent.com/26381804/327939648-a6f3f3b3-a73b-4165-b584-444f85079ccf.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MjU1MzM2NDEsIm5iZiI6MTcyNTUzMzM0MSwicGF0aCI6Ii8yNjM4MTgwNC8zMjc5Mzk2NDgtYTZmM2YzYjMtYTczYi00MTY1LWI1ODQtNDQ0Zjg1MDc5Y2NmLnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNDA5MDUlMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjQwOTA1VDEwNDkwMVomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPTdjZTZkY2FhYjkyOTI3MjY3MzZmZDhmMzA1MWIwNzI4Zjg5YTRlYzNkOTUyZGQ2OTczODJlYjA4OGVjN2U3MzkmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0JmFjdG9yX2lkPTAma2V5X2lkPTAmcmVwb19pZD0wIn0.eKvDKuCCzaxTZfnH3gjwqKwBJN_tOoMBlh-MlVcUU4U)
No log bundle at this time.
The text was updated successfully, but these errors were encountered: