Troubleshooting the global Cluster on Huawei Cloud Stack

For the installation stages and the failures every provider shares, see Troubleshooting. The following are specific to Huawei Cloud Stack. 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 cannot reach the IAM endpointCheck externalGlobalDomain and schema in install-config.yaml, and that the bootstrap node resolves and reaches iam-apigateway-proxy.<externalGlobalDomain> on TCP/443, or TCP/80 for http. Then run create again.
Stage 4 does not advanceRead the provider log: <extract-dir>/res/<arch>/ac --kubeconfig /var/cpaas/data/alauda.kubeconfig -n cpaas-system logs deployment/cluster-api-provider-hcs-manager --tail=50. If it names quota or an address that is in use, free it in HCS. Otherwise, contact technical support with the log.
Stage 5 does not advanceCheck that the bootstrap node is in the VPC of the cluster (see Prerequisites). If it is in another VPC, contact technical support. Otherwise, check that it reaches the control plane VIP on TCP/6443, and fix the network. If it reaches the VIP, contact technical support.
An instance is created but never joinsCheck that the node reaches the control plane endpoint on TCP/6443 and the registry, through the subnet and the security group, and fix the network. If the node reaches both, contact technical support.

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