VKS clusters will not create regardless of being created from VCFA or through Local Consumption Interface (LCI).
In the Supervisor cluster context, the following symptoms are observed:
kubectl get cluster,machine,vspheremachine,vm -o wide -n <namespace>
kubectl describe vm -n <namespace> <vm name>
message: 'failed to cache files: failed to cache storage items: failed to check if file exists: 500 Internal Server Error'
kubectl get pods -n vmware-system-vmop
kubectl logs -n vmware-system-vmop -c manager <vmware-system-vmop-controller-manager-id>
IMMDD HH:MM:SS.ssssss 1 recorder.go:104] "failed to cache files: failed to cache storage items: failed to check if file exists: 500 Internal Server Error" logger="events" type="Warning" object={"kind":"VirtualMachine","namespace":"<namespace>","name":"<vks cluster name>","uid":"<uid>","apiVersion":"vmoperator.vmware.com/v1alpha5","resourceVersion":"######"} reason="CreateFailure"
EMMDD HH:MM:SS.ssssss 1 controller.go:474] "Reconciler error" err="failed to cache files: failed to cache storage items: failed to check if file exists: 500 Internal Server Error" logger="virtualmachine-controller" VirtualMachine="<namespace>/<vks cluster name>"
In the vCenter, vpxd logs report the following error across one or more host-ids:
YYYY-MM-DDTHH:MM:SS.sssZ INFO vpxd #### [vc@4413 sub="vmomi.soapStub[##]" opID="<opID>"] SOAP request returned HTTP failure; <, /hgw/<host-id>/vpxa>, method: retrieveVStorageObject; code: 500(Internal Server Error); fault: (vim.fault.NotFound) {
On the ESXi host where the VM is trying to provision, the following error is found in hostd logs:
WARNING Hostd <id> [esx@#### sub="Default" opID="<opID>" user="vpxuser:VSPHERE.LOCAL\wcp-vmop-user-<userid>"] Vslm Failure: VslmRetrieveDisk failed for fcd <FCD ID> on datastore /vmfs/volumes/<location>/ with type vim.fault.NotFound, N3Vim5Fault8NotFound9ExceptionE(Fault cause: vim.fault.NotFound
vSphere Supervisor
vSphere Cloud Foundation 9.X
A stale or orphaned FCD in the environment is preventing the creation of VMs for VKS cluster nodes.
A reconciliation on the datastores in the environment will clean up any stale or orphaned FCDs, including the FCD causing this issue.
See Reconciling Discrepancies in the Managed Virtual Disk Catalog
NOTE: Depending on the size of the environment, datastore reconciliation task may show success but may not fully take effect for at least 2 hours.