<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Deployment failure: &amp;quot;unable to wait for post customization phase&amp;quot; in VMware Cloud Director Container Service Extension Discussions</title>
    <link>https://communities.vmware.com/t5/VMware-Cloud-Director-Container/Deployment-failure-quot-unable-to-wait-for-post-customization/m-p/2923256#M87</link>
    <description>&lt;P&gt;Hi &lt;a href="https://communities.vmware.com/t5/user/viewprofilepage/user-id/5570622"&gt;@jleavers1&lt;/a&gt; ,&lt;/P&gt;&lt;P&gt;I believe this is a duplicate of &lt;A href="https://communities.vmware.com/t5/VMware-Cloud-Director-Container/Deployment-failure-unable-to-wait-for-post-customization-phase/m-p/2922851#M75" target="_blank"&gt;https://communities.vmware.com/t5/VMware-Cloud-Director-Container/Deployment-failure-unable-to-wait-for-post-customization-phase/m-p/2922851#M75&lt;/A&gt;.&lt;/P&gt;&lt;P&gt;As &lt;a href="https://communities.vmware.com/t5/user/viewprofilepage/user-id/5566246"&gt;@lzichong&lt;/a&gt; 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.&lt;/P&gt;&lt;P&gt;Thank you!&lt;/P&gt;</description>
    <pubDate>Wed, 10 Aug 2022 22:32:26 GMT</pubDate>
    <dc:creator>shamasundara</dc:creator>
    <dc:date>2022-08-10T22:32:26Z</dc:date>
    <item>
      <title>Deployment failure: "unable to wait for post customization phase"</title>
      <link>https://communities.vmware.com/t5/VMware-Cloud-Director-Container/Deployment-failure-quot-unable-to-wait-for-post-customization/m-p/2922846#M72</link>
      <description>&lt;P&gt;Deployment is failing with following shown in journalctl output:&lt;/P&gt;&lt;P&gt;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]"}&lt;BR /&gt;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]"}&lt;BR /&gt;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"}&lt;BR /&gt;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)]"}&lt;/P&gt;</description>
      <pubDate>Mon, 08 Aug 2022 19:51:35 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-Cloud-Director-Container/Deployment-failure-quot-unable-to-wait-for-post-customization/m-p/2922846#M72</guid>
      <dc:creator>jleavers1</dc:creator>
      <dc:date>2022-08-08T19:51:35Z</dc:date>
    </item>
    <item>
      <title>Re: Deployment failure: "unable to wait for post customization phase"</title>
      <link>https://communities.vmware.com/t5/VMware-Cloud-Director-Container/Deployment-failure-quot-unable-to-wait-for-post-customization/m-p/2923256#M87</link>
      <description>&lt;P&gt;Hi &lt;a href="https://communities.vmware.com/t5/user/viewprofilepage/user-id/5570622"&gt;@jleavers1&lt;/a&gt; ,&lt;/P&gt;&lt;P&gt;I believe this is a duplicate of &lt;A href="https://communities.vmware.com/t5/VMware-Cloud-Director-Container/Deployment-failure-unable-to-wait-for-post-customization-phase/m-p/2922851#M75" target="_blank"&gt;https://communities.vmware.com/t5/VMware-Cloud-Director-Container/Deployment-failure-unable-to-wait-for-post-customization-phase/m-p/2922851#M75&lt;/A&gt;.&lt;/P&gt;&lt;P&gt;As &lt;a href="https://communities.vmware.com/t5/user/viewprofilepage/user-id/5566246"&gt;@lzichong&lt;/a&gt; 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.&lt;/P&gt;&lt;P&gt;Thank you!&lt;/P&gt;</description>
      <pubDate>Wed, 10 Aug 2022 22:32:26 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-Cloud-Director-Container/Deployment-failure-quot-unable-to-wait-for-post-customization/m-p/2923256#M87</guid>
      <dc:creator>shamasundara</dc:creator>
      <dc:date>2022-08-10T22:32:26Z</dc:date>
    </item>
  </channel>
</rss>

