setup.sh exits with an error in its preflight checks | The host is unchanged. Fix the cause it names, then run create again. |
setup.sh exits with an error after its preflight checks | In the directory of setup.sh, run bash cleanup.sh -y, then run create again. cleanup.sh -y reboots the host and deletes /root/.kube. |
create reports conflict with prepared input when it submits the installation | global.registry (the address or the credentials) changed after the bootstrap cluster started. From that point on, the value is fixed, and the installation cannot continue with a new value. Restore the original values and run create again. To use the new values instead, run bash cleanup.sh -y in the directory of setup.sh, then run create again. |
| Stage 2 does not advance | Check the provider releases and Pods with <extract-dir>/res/<arch>/ac --kubeconfig /var/cpaas/data/alauda.kubeconfig get apprelease -A and <extract-dir>/res/<arch>/ac --kubeconfig /var/cpaas/data/alauda.kubeconfig get pods -A. If an image or chart cannot be pulled, upload the payload again as described in Prepare the Target-Version Payload, then run create again. Otherwise, contact technical support. |
| Stage 4 does not advance | Run <extract-dir>/res/<arch>/ac --kubeconfig /var/cpaas/data/alauda.kubeconfig -n cpaas-system describe machine <name>, then see the provider's troubleshooting page. |
| Stage 5 does not advance | If the control plane endpoint is an external load balancer, check its health check first. On a host in the network from which the load balancer sends its health checks, run curl -kfsS https://<control-plane-node-ip>:6443/healthz, where <control-plane-node-ip> is the address of the first control plane node. If the output is not ok, correct the network path or firewall rules between that network and the control plane node. If the output is ok, or if you use a Self-built VIP, run <extract-dir>/res/<arch>/ac --kubeconfig /var/cpaas/data/alauda.kubeconfig -n cpaas-system describe kubeadmcontrolplane global-control-plane and read its conditions. Then see the provider's troubleshooting page, or contact technical support. |
Stage 5 shows readyReplicas: 0 | This is expected. The nodes stay NotReady until the platform installs the network plugin in stage 6. Continue. |
| Stage 6 stalls | On the bootstrap node, read the last lines and the latest error in /var/cpaas/data/installer.log, and fix the cause that the log names. The installer retries by itself. If the error does not name a cause that you can fix, contact technical support. |
| Stage 8 reports no running installer Pod | ac removes the bootstrap cluster only after it has copied the installer log. Wait until <extract-dir>/res/<arch>/ac --kubeconfig /var/cpaas/data/alauda.kubeconfig -n cpaas-system get pods shows the cpaas-installer Pod Running, then run create again. If the Pod does not return to Running, contact technical support. |
| Stage 8 waits for a provider | On a machine with ac (on the bootstrap node, <extract-dir>/res/<arch>/ac), run these commands in order: ac login https://<platform-address> --name <session-name> as the platform administrator, then ac config use-cluster global, then ac get moduleconfigs | grep cluster-api-provider. If both providers are listed, continue to wait. Otherwise, contact technical support. |
| Nodes cannot pull images | Check that the registry is reachable from the node network. If the payload is incomplete, upload it again as described in Prepare the Target-Version Payload. |