Troubleshooting the global Cluster on Huawei DCS

For the installation stages and the failures every provider shares, see Troubleshooting. The following are specific to Huawei DCS. Run the commands below on the bootstrap node; unless a row says otherwise, they read the bootstrap cluster, which exists until the installation completes. If /var/cpaas/data/alauda.kubeconfig is missing, see Common Failures.

ResultAction
Preflight reports a name that was not foundCorrect the name and its type in install-config.yaml against the DCS site named in the message, then run create again.
Preflight cannot sign inCorrect endpoint, authUser, authKey, site, and userType in install-config.yaml, then run create again. authKey is the plain-text password and site the bare site ID. Do not run create again before you correct them: repeated failed sign-ins lock the DCS account.
Stage 4 does not advanceRun <extract-dir>/res/<arch>/ac --kubeconfig /var/cpaas/data/alauda.kubeconfig -n cpaas-system describe dcsmachine <name>. If the conditions name datastore capacity or an address that is in use, free it on DCS. Otherwise, contact technical support.
A VM is created but never joinsFrom 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.
The control plane VMs land on one host with controlPlaneHA: trueCheck the requirements in Control Plane Spread and whether DRS migration is blocked. If they are met, contact technical support.
curl … /healthz through the Self-built VIP does not print okCheck 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.

For provider failures that also apply after installation, see Troubleshooting Huawei DCS Workload Clusters.