If vmware-vsphere-csi-driver-operator cannot sync a storage policy to the vCenter, the cluster looks Available: true and Degraded: false, without any indication that something is wrong.
But the operator cannot create the default storage class!
vmware-vsphere-csi-driver-operator logs:
2025-06-19T14:21:48.396359602Z I0619 14:21:48.396254 1 reflector.go:376] Caches populated for operator.openshift.io/v1, Resource=clustercsidrivers from k8s.io/client-go@v0.32.2/tools/cache/reflector.go:251 2025-06-19T14:21:48.775450505Z I0619 14:21:48.775412 1 reflector.go:376] Caches populated for *v1.ClusterCSIDriver from k8s.io/client-go@v0.32.2/tools/cache/reflector.go:251 2025-06-19T14:24:04.576692316Z I0619 14:24:04.576531 1 vmware.go:308] Updated category openshift-j-mdr-i1-p-34-rv5xz with associated types 2025-06-19T14:28:43.886043400Z E0619 14:28:43.885996 1 storageclasscontroller.go:115] error syncing storage policy for vcenter7-ocs4.lab.eng.blr.redhat.com: error tagging datastore /Datacenter-ECO/datastore/vsanDatastore with j-mdr-i1-p-34-rv5xz: error finding tag j-mdr-i1-p-34-rv5xz: get category urn:vmomi:InventoryServiceTag:5d55ac33-8afa-4799-a6bb-2e48e21419c9:GLOBAL failed for Get "https://vcenter7-ocs4.lab.eng.blr.redhat.com/rest/com/vmware/cis/tagging/tag/id:urn:vmomi:InventoryServiceTag:5d55ac33-8afa-4799-a6bb-2e48e21419c9:GLOBAL": context deadline exceeded