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

Bug 1814304

Summary:	Include the VMware permissions for dynamic provisioning
Product:	OpenShift Container Platform	Reporter:	Christian Huffman <chuffman>
Component:	Documentation	Assignee:	Vikram Goyal <vigoyal>
Status:	CLOSED DUPLICATE	QA Contact:	Xiaoli Tian <xtian>
Severity:	high	Docs Contact:	Vikram Goyal <vigoyal>
Priority:	high
Version:	4.5	CC:	aos-bugs, hekumar, jokerman
Target Milestone:	---
Target Release:	4.7.0
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-11-12 14:57:46 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 Christian Huffman 2020-03-17 15:26:14 UTC

It seems that there's a moderately common issue of customers not having enough permissions to provision volumes after installing vmware with UPI. For instance, the following two sources:

http://post-office.corp.redhat.com/archives/openshift-docs/2020-March/msg00013.html

https://bugzilla.redhat.com/show_bug.cgi?id=1790658

Dynamically provisioning storage is a task we can expect the majority of our customers to perform, and we should highlight these permissions. Is it possible to bring more attention to step 8 of https://docs.openshift.com/container-platform/4.3/installing/installing_vsphere/installing-vsphere.html#installation-vsphere-config-yaml_installing-vsphere , and possibly include these in the prerequisites as a note?

Comment 2 Hemant Kumar 2020-11-12 14:57:46 UTC


*** This bug has been marked as a duplicate of bug 1869035 ***