Error while bootstrapping the machine error occurs when attempting to deploy a cluster with VMware Cloud Director Container Service Extension

Products

• VMware Cloud Director

Issue/Introduction

• When deploying a cluster there is an error for the EPHEMERAL-TEMP-VM similar to the following:
  
  [error while bootstrapping the machine... unable to wait for post customization phase [guestinfo.cloudinit.kind.binary.install.status] : [invalid postcustomization phase: [failed] for key [guestinfo.cloudinit.kind.binary.install.status] for vm [EPHEMERAL-TEMP-VM] due to :[ctr image pull https://projects.packages.broadcom.com/$1/$2]]] during cluster creation
  
  
• The fully qualified domain name projects.packages.broadcom.com is resolvable from the ephemeral virtual machine.
• The Container Registry URL is set to https://projects.packages.broadcom.com.
• The Container Registry URL is set to projects.registry.vmware.com or projects.packages.broadcom.com

Environment

VMware Cloud Director Container Service Extension 4.2.x
VMware Cloud Director 10.5.1

Cause

• Retrieving an image via the ctr command (i.e., ctr image pull) does not expect the repository to include a URL scheme such as https://. Thus, setting the Container Registry URL to https://projects.packages.broadcom.com will cause the deployment to fail since it will be unable to retrieve the image from the repository.

• The issue is also caused by failure to access the Tanzu package repositories.

• The projects.registry.vmware.com repository address is no longer available and has been replaced with projects.packages.broadcom.com. The current recommended address for publicly accessible images is projects.packages.broadcom.com.

Resolution

1. Update Container Registry URL to the fully qualified domain name for the repository without the URL scheme using the instructions from the following document:
   
   Configure the VMware Cloud Director Container Service Extension Server Settings
   
   For example, instead of https://projects.packages.broadcom.com, specify projects.packages.broadcom.com. 
   Do not use projects.registry.vmware.com repository address as its been deprecated.
2. Please follow the KB or whitelisting the domains required. 
3. Restart the VMware Cloud Director Container Service Extension Server vApp to apply the new configuration.

Additional Information

This issue can also occur for custom or air-gapped configurations if the specified repository address is configured with the URL scheme.

For information on creating a local container registry, please refer to the following document:

Create an Air-gapped Environment