VMware BMA Deployment Failure

Deploment of Cloud Native VMware BMA does not complete as bma-core-cn-final-mysqldb-0 and bma-core-cn-final-object-storage-0 are not running.

Problem

During the installation of VMware BMA Core, pods such as bma-core-cn-final-mysqldb-0 and bma-core-cn-final-object-storage-0 does not come up.

Cause

The status appear as pending when you run kubectl get pvc as given below.

The following error about vsan health appears when you describe the pvc pod.

external provisioner "csi.vsphere.vmware.com" or manually created by system administrator
  Normal   Provisioning          2m58s (x14 over 23m)  csi.vsphere.vmware.com_vsphere-csi-controller-74d4c87695-jm24g_0fc6520a-b732-494a-aa18-e1066aa8fef1  External provisioner is provisioning volume for claim "default/vmware-bma-core-object-storage-volume-vmware-bma-core-object-storage-0"
  Warning  ProvisioningFailed    2m58s (x14 over 23m)  csi.vsphere.vmware.com_vsphere-csi-controller-74d4c87695-jm24g_0fc6520a-b732-494a-aa18-e1066aa8fef1  failed to provision volume with StorageClass "vsphere-sci": rpc error: code = Internal desc = failed to create volume. Error: POST "/vsanHealth": 503 Service Unavailable

Solution

Verify that vsan-health-service is started in VMware Vsphere and if not, start vsan-health-service because vsphere-csi relies on vsan-health-service.