Bug 1859341
| Summary: | Unable to Create PVC with default thin Storage Class after 4.5 UPI Install on VMware | ||||||
|---|---|---|---|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Chris Keller <ckeller> | ||||
| Component: | Documentation | Assignee: | Vikram Goyal <vigoyal> | ||||
| Status: | CLOSED DUPLICATE | QA Contact: | Xiaoli Tian <xtian> | ||||
| Severity: | unspecified | Docs Contact: | Vikram Goyal <vigoyal> | ||||
| Priority: | unspecified | ||||||
| Version: | 4.5 | CC: | adahiya, aos-bugs, hekumar, jokerman, jritter, nschuetz | ||||
| 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-07-24 16:40:16 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: | |||||||
| Attachments: |
|
||||||
Yes the path to the folder should be taken from install-config's cluster name. To unblock the install while we debug this issue, can you edit the cloudprovider config and fix the folder name? This can be done via: ~> oc edit cm cloud-provider-config -n openshift-config and put right folder name in the cloud-config. Thanks Hemant, that resolved the issue:
$ oc get pvc test -n default
NAME STATUS VOLUME CAPACITY ACCESS MODES STORAGECLASS AGE
test Bound pvc-4c6f9618-6141-4181-b4e9-a994428e71d7 1Gi RWO thin 2m57s
I noticed in the installer manifests manifests/cloud-provider-config.yaml is generated as such:
apiVersion: v1
data:
config: |
[Global]
secret-name = "vsphere-creds"
secret-namespace = "kube-system"
insecure-flag = "1"
[Workspace]
server = "vsphere.pwc.umbrella.local"
datacenter = "PWC"
default-datastore = "pool-nvme-vms"
folder = "/PWC/vm/vmware-upi-wlsjg"
[VirtualCenter "vsphere.pwc.umbrella.local"]
datacenters = "PWC"
kind: ConfigMap
metadata:
creationTimestamp: null
name: cloud-provider-config
namespace: openshift-config
There is also a reference to the IPI style name in manifests/cluster-infrastructure-02-config.yml.
*** This bug has been marked as a duplicate of bug 1849434 *** |
Created attachment 1701977 [details] Example install-config.yaml Description of problem: After doing a UPI deployment of OpenShift 4.5 on VMware, unable to create PVCs using default thin storage class. Version-Release number of selected component (if applicable): $ openshift-install version openshift-install 4.5.2 built from commit 6336a4b3d696dd898eed192e4188edbac99e8c27 release image quay.io/openshift-release-dev/ocp-release@sha256:8f923b7b8efdeac619eb0e7697106c1d17dd3d262c49d8742b38600417cf7d1d How reproducible: Always. Steps to Reproduce: 1. Follow VMware UPI installation instructions for OpenShift 4.5 2. Attempt to create a PVC using the default thin storage class Actual results: PVC hangs in Pending stage. Output shows the following: $ oc describe pvc test Name: test Namespace: default StorageClass: thin Status: Pending Volume: Labels: <none> Annotations: volume.beta.kubernetes.io/storage-provisioner: kubernetes.io/vsphere-volume Finalizers: [kubernetes.io/pvc-protection] Capacity: Access Modes: VolumeMode: Filesystem Mounted By: <none> Events: Type Reason Age From Message ---- ------ ---- ---- ------- Warning ProvisioningFailed 30s (x18 over 24m) persistentvolume-controller Failed to provision volume with StorageClass "thin": folder '/PWC/vm/vmware-upi-b9xz5' not found Expected results: PVC is successfully provisioned. Additional info: The install seems to be using an IPI generated cluster name for the folder path. Since this is a UPI installation, should the cluster name be taken directly from install-config.yaml (attached)? For example: '/PWC/vm/vmware-upi'