Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1878262

Summary:	update documentation to state that using SecureBoot on VMware is currently unsupported
Product:	OpenShift Container Platform	Reporter:	Micah Abbott <miabbott>
Component:	Documentation	Assignee:	Vikram Goyal <vigoyal>
Status:	CLOSED NOTABUG	QA Contact:	Xiaoli Tian <xtian>
Severity:	unspecified	Docs Contact:	Vikram Goyal <vigoyal>
Priority:	unspecified
Version:	4.6	CC:	aos-bugs, bgilbert, jima, jokerman
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-09-16 20:08:08 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 Micah Abbott 2020-09-11 17:52:52 UTC

Document URL: https://docs.openshift.com/container-platform/4.5/installing/installing_vsphere/installing-vsphere-installer-provisioned.html#prerequisites

Suggestions for improvement: Advise users that configuring SecureBoot when using VMware is not supported

Additional information:  In https://bugzilla.redhat.com/show_bug.cgi?id=1877995d, it was reported that booting RHCOS nodes with SecureBoot enabled in a VMWare environment failed.  Initial investigation of the issues shows that it is unlikely to be fixed quickly.

Additionally, this limitation may extend to older versions of RHCOS/OCP

Comment 1 Benjamin Gilbert 2020-09-15 04:01:26 UTC

On previous versions of RHCOS, VMware Secure Boot would have worked with the bare-metal install flow at least.  Also, bug 1877995 includes comments implying that Secure Boot problems were previously considered a blocker.  We should probably investigate further before proceeding with a docs change.

Comment 2 Micah Abbott 2020-09-16 20:08:08 UTC

I was hasty with my request; we'll need to address the issue in BZ#1877995 as part of 4.6.  Closing this.