VKS Workload Cluster Creation Stuck in Creating State Due to Content Library Access Failure
search cancel

VKS Workload Cluster Creation Stuck in Creating State Due to Content Library Access Failure

book

Article ID: 425296

calendar_today

Updated On:

Products

Tanzu Kubernetes Runtime VMware vSphere Kubernetes Service

Issue/Introduction

VKS Workload Cluster creation remains stuck in the Creating state.
The control plane (master) node stays in Provisioning state, while worker nodes remain Pending.

When describing the control plane Machine object, it shows that it is waiting for the control plane to be initialized. However, the control plane VM is never successfully created.

Cause

The issue occurs because vCenter is unable to access the Content Library due to incorrect DNS configuration.
The vCenter FQDN does not resolve to the correct IP address, resulting in failed image retrieval during cluster provisioning.

This is confirmed by errors in the VM Operator (vmop) logs, similar to the following:

Reconciler error: failed to find image: GET https://<vcenter_fqdn>/content/library: 404 Not Found

Resolution

  1. Verify DNS configuration for the vCenter FQDN.

  2. Ensure the vCenter FQDN resolves to the correct IP address from:

    • Supervisor Control Plane VMs

    • ESXi hosts

  3. Correct the DNS records as needed.

  4. Once DNS resolution is fixed, retry the workload cluster creation or allow the reconciliation process to continue.

After correcting the DNS configuration, the control plane VM is created successfully, worker nodes proceed from Pending to Running, and the workload cluster creation completes as expected.