| Preflight reports a name that was not found | Correct the name in install-config.yaml, then run create again. Preflight stops at the first missing object, so repeat until it passes. With several compute resources in the datacenter, set computeResource to the name of one. |
| Preflight passes, but a VM is not created because a datastore, folder, or port group is not found | Contact technical support to correct the inventory path. |
| Preflight cannot sign in | Correct server, username, and password in install-config.yaml, check that vCenter answers on TCP/443 from the bootstrap node, then run create again. |
| Stage 4 does not advance | Run <extract-dir>/res/<arch>/ac --kubeconfig /var/cpaas/data/alauda.kubeconfig -n cpaas-system describe vspheremachine <name> and <extract-dir>/res/<arch>/ac --kubeconfig /var/cpaas/data/alauda.kubeconfig -n cpaas-system describe vspherevm <name>. If the conditions name datastore capacity, free space on it. Otherwise, contact technical support. |
| A VM is created but never joins | From the VM console, check that the node reaches the control plane endpoint on TCP/6443 and the registry, with the gateway and DNS from install-config.yaml, and fix the network. If the node reaches both, contact technical support. |
| Nodes stay uninitialized after the platform installation | Before the handover, run <extract-dir>/res/<arch>/ac --kubeconfig /var/cpaas/data/alauda.kubeconfig -n cpaas-system get clusterresourcesetbinding global -o yaml and check that global-vsphere-cpi is applied. After the handover, check the CPI Pods on the global cluster. If neither shows a cause, contact technical support. |
| Stage 8 waits for the credential | Check that cpaas-system/global-credential exists on the global cluster and is not terminating. If it is missing or stays terminating, contact technical support. |
curl … /healthz through the Self-built VIP does not print ok | Check that the network allows VRRP (IP protocol 112, multicast 224.0.0.18) and gratuitous ARP between the control plane nodes, and that no other VRRP instance in the Layer 2 domain uses the vrid. If both are met, contact technical support. |