Thin StorageClass PVCs remain in Pending state indefinitely
Issue
- Persistent volume claims provisioned from the thin StorageClass using the OpenShift vSphere cloud provider remain in
Pending
indefinitely. - The claim remains in a
Pending
state without any indication fromoc describe pvc
as to why this is occurring. - A
VMDK
is created on the specified datastore, but thePVC
never binds and theVMDK
stays0KB
. - The following logs are repeated in the active master
kube-controller-manager
pod:
I0101 00:20:52.420678 1 pv_controller.go:334] synchronizing unbound PersistentVolumeClaim[openshift-kube-controller-manager/testpvc1]: no volume found
I0101 00:20:52.420720 1 pv_controller.go:1342] provisionClaim[openshift-kube-controller-manager/testpvc1]: started
I0101 00:20:52.420752 1 pv_controller.go:1614] scheduleOperation[provision-openshift-kube-controller-manager/testpvc1[2edae8cf-4794-11ea-b1ab-0050569ea5ea]]
I0101 00:20:52.420781 1 pv_controller.go:1625] operation "provision-openshift-kube-controller-manager/testpvc1[2edae8cf-4794-11ea-b1ab-0050569ea5ea]" is already running, skipping
(...)
I0101 00:21:37.421228 1 pv_controller_base.go:170] enqueued "openshift-kube-controller-manager/testpvc1" for sync
I0101 00:21:37.421263 1 pv_controller_base.go:356] claimWorker[openshift-kube-controller-manager/testpvc1]
I0101 00:21:37.421285 1 pv_controller_base.go:518] storeObjectUpdate updating claim "openshift-kube-controller-manager/testpvc1" with version 460169
I0101 00:21:37.421313 1 pv_controller.go:247] synchronizing PersistentVolumeClaim[openshift-kube-controller-manager/testpvc1]: phase: Pending, bound to: "", bindCompleted: false, boundByController:
Environment
- Red Hat OpenShift Container Platform (RHOCP) 4.x
- Red Hat OpenShift Data Foundation (RHODF) 4.x
- VMware vSphere
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.