Bug 1878262 - update documentation to state that using SecureBoot on VMware is currently unsupported
Summary: update documentation to state that using SecureBoot on VMware is currently un...
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Documentation
Version: 4.6
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: Vikram Goyal
QA Contact: Xiaoli Tian
Vikram Goyal
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-09-11 17:52 UTC by Micah Abbott
Modified: 2020-09-16 20:08 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-09-16 20:08:08 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

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.


Note You need to log in before you can comment on or make changes to this bug.