VCFA deployment fails with LCMVSPHERECONFIG100009 timed out waiting for the condition on kubernetesclusters/vcf-mgmt-#######

Products

• VCF Operations/Automation (formerly VMware Aria Suite)

Issue/Introduction

• When deploying VCFA from SDDC Manager/ Lifecycle, it fails due to a timeout waiting on the kubernetes cluster.
• VMSP template is successfully copied to the destination vCenter.
• No activity occurs in vCenter after the initial copy of the template.
• After 2 hours the task fails with the above error in SDDC Manager/ Lifecycle.
• Your destination vCenter is configured with 10.244.0.0/16.

Environment

SDDC-Manager 9.0

VCFA 9.0

Cause

During deployment, SDDC-Manager/ Lifecycle will copy the VMSP template to vCenter, then deploy a kind cluster on the Fleet Mgmt server to facilitate the installation of VCFA on the destination VC/ deployed VMSP appliance(s).

This cluster is configured using 10.244.0.0/16 which can be a duplicate of other resources in your environment (such as vCenter) causing a conflict.

Resolution

This issue is resolved in VCF 9.0.1

Workaround:

VCFA 9.0.0 uses a fixed subnet (10.244.0.0/16) for deployment configurations. To use a different subnet, add a networking section to the bootstrap.sh file:

1. SSH into the fleet management appliance.
2. Backup the file using:

   • cp /data/vmsp/scripts/bootstrap.sh /tmp/bootstrap.sh.bku 

3. Edit the file:

   • vi /data/vmsp/scripts/bootstrap.sh

4. Locate the correct section and add the following two networking lines (highlighted in red):

   • # Create Kind config
     
     # containerd will forward traffic for the registry to the nodePort service
     
     # A similar configuration will be set on the new cluster through kubeadm in the vmsp-configs chart
     
     cat <<EOF >"${KIND_CONFIG}"
     
     kind: Cluster
     
     apiVersion: kind.x-k8s.io/v1alpha4
     
       networking:
     
         podSubnet: "10.255.0.0/16"
     
     kubeadmConfigPatches:
     
     - |
     
       apiVersion: kubeadm.k8s.io/v1beta3

5. Save the file.
6. Re-attempt the deployment (either through SDDC-Manager/ Lifecycle or from your initial VCF 9 deployment appliance).