The default wait time for CreateKindVM and PostCustomizationPhases is too short

steven0301 — Wed, 17 Aug 2022 09:07:31 GMT

The default wait time for CreateKindVM is 180 seconds, if the time taken more than that, the creation of cluster will be blocked or panic. In my env (a cassini testbed), the process of CreateKindVM took about 480 seconds. To make it work, I have to modify the source code to increase the default value and build a temp version to replace the binary in the CSE server VM.

The same issue for ClusterCreatePostCustomizationPhases of "guestinfo.cloudinit.target.cluster.ready.status", the default wait time is 1800 seconds, but in my env, it could take more than that time - it took about 1500 seconds in one run, and took more than 1800 seconds in another run.

Can you increase the default values for these two items or make them configurable?

ScriptExecutionError while deploying a cluster

steven0301 — Mon, 08 Aug 2022 07:22:36 GMT

The cluster events show ScriptExecutionError and the cluster is in "NOT Ready" status for ever.

Found some errors in the logs.

E0808 03:26:47.018187 1 controller.go:188] controller/kubeadmcontrolplane "msg"="Failed to update KubeadmControlPlane Status" "error"="failed to create remote cluster client: failed to retrieve kubeconfig secret for Cluster capvcd-cluster3-ns/capvcd-cluster3: secrets \"capvcd-cluster3-kubeconfig\" not found" "cluster"="capvcd-cluster3" "name"="capvcd-cluster3-control-plane" "namespace"="capvcd-cluster3-ns" "reconciler group"="controlplane.cluster.x-k8s.io" "reconciler kind"="KubeadmControlPlane"

The log bundle is attached.

Could some help to take a look?

steven0301 Tracker

The default wait time for CreateKindVM and PostCustomizationPhases is too short

ScriptExecutionError while deploying a cluster