- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Deployment failure: "unable to wait for post customization phase"
Deployment is failing with following shown in journalctl output:
Aug 08 19:43:38 photon bash[2574]: {"level":"info","ts":1659987818.9050834,"caller":"utils/rdeUtils.go:210","msg":"Assigning value [Elpased time waiting for postcustomization status [guestinfo.cloudinit.kind.cluster.creation.status] to complete [0.240771] seconds] to key [HeartbeatString] in [types.VCDKEStatus]"}
Aug 08 19:43:38 photon bash[2574]: {"level":"info","ts":1659987818.939308,"caller":"utils/rdeUtils.go:313","msg":"successfully updated defined entity with ID [urn:vcloud:entity:vmware:capvcdCluster:8319ce29-cba5-4f65-8f20-46d0207cb386]"}
Aug 08 19:43:49 photon bash[2574]: {"level":"error","ts":1659987829.103915,"caller":"cluster/clusterManager.go:238","msg":"error waiting for creation of cluster [test-1(urn:vcloud:entity:vmware:capvcdCluster:8319ce29-cba5-4f65-8f20-46d0207cb386)]: [error while bootstrapping the machine [test-1/EPHEMERAL_TEMP_VM]; unable to wait for post customization phase [guestinfo.cloudinit.kind.cluster.creation.status] : [invalid postcustomization phase: [failed] for key [guestinfo.cloudinit.kind.cluster.creation.status] for vm [EPHEMERAL_TEMP_VM]]]","stacktrace":"gitlab.eng.vmware.com/core-build/vcd-k8s-provider/src/cluster.CreateCluster\n\t/app/src/cluster/clusterManager.go:238\nmain.processRDE\n\t/app/main.go:566"}
Aug 08 19:43:49 photon bash[2574]: {"level":"info","ts":1659987829.1040707,"caller":"repair/heartbeat.go:102","msg":"updating component [{errorSet {ScriptExecutionError 2022-08-08 19:43:49.103954454 +0000 UTC m=+6717.591647529 urn:vcloud:vm:4fd80e53-7307-43fc-b74f-274f33aabb5e map[Detailed Error:[error while bootstrapping the machine [test-1/EPHEMERAL_TEMP_VM]; unable to wait for post customization phase [guestinfo.cloudinit.kind.cluster.creation.status] : [invalid postcustomization phase: [failed] for key [guestinfo.cloudinit.kind.cluster.creation.status] for vm [EPHEMERAL_TEMP_VM]]] during cluster creation]} false}] in RDE: [test-1(urn:vcloud:entity:vmware:capvcdCluster:8319ce29-cba5-4f65-8f20-46d0207cb386)]"}
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi @jleavers1 ,
I believe this is a duplicate of https://communities.vmware.com/t5/VMware-Cloud-Director-Container/Deployment-failure-unable-to-wait-....
As @lzichong said, could you please check the default sizing policy of the VDC and verify if the default sizing policy has at least 2 cores and 4GB memory? CSE 4.0 creates an intermediary VM (having the default sizing policy) with kind cluster installed on it which requires at least 2 cores and 4 GB memory.
Thank you!