WCP Supervisor enablement fails with PMan orchestration error

Products

VMware vSphere Kubernetes Service VMware vCenter Server

Issue/Introduction

During the enablement of Supervisor Management or Workload Management, the workflow task remains in a 'Configuring' status. The vSphere Client displays the following underlying task states:

Installed and Started Kubernetes Node Agent on the ESXi Host (Pending)
Configured ESXi Host as Kubernetes Worker Node
Kubernetes Worker Node is schedulable
Kubernetes Worker Node commit work done in vSphere

All Host in status "configuring"

The vSphere Client reports 'Apply Solution' task fails with the following error:

Apply Solution

A general system error occurred: Solution specification in the image are incompatible with hosts 'host-01.example.com, host-02.example.com, host-03.example.com'

The vCenter Server WCP logs at /var/log/vmware/wcp/wcpsvc.log report entries similar to the following:

[timestamp] error wcp [pman/client.go:659] [opID=26bd324c-2810-4ea4-####-d7bb1beaa308-host-##-vLCM:AddHost:domain-c##:host-##] PMan API: Task Get for Apply Task API: Attempt#[6]:Failed Attempts:[0] of MaxFailedAttemps[1]Error Message: Solution specification in the image are incompatible with hosts 'host-01.example.com, host-02.example.com, host-03.example.com'
[timestamp] error wcp [kubelifecycle/pman_client.go:373] [opID=26bd324c-2810-4ea4-####-d7bb1beaa308-host-##-vLCM:AddHost:domain-c##:host-##] PMan API: Task Get for Apply Task API: Attempt#[6]:Failed Attempts:[0] of MaxFailedAttemps[1]Error Type: ERROR

The vCenter Server VUM logs at /var/log/vmware/vmware-updatemgr/vum-server/vmware-vum-server.log report entries similar to the following:

[timestamp] info vmware-vum-server[79#49] [Originator@6876 sub=ClusterApplySolutionTask] [Task, 524] Task:com.vmware.vcIntegrity.lifecycle.ClusterApplySolutionTask ID:52fe11b8-a26d-334e-####-d3791449f3df. Finalize host(=host-##) status(=1)
[timestamp] error vmware-vum-server[79#49] [Originator@6876 sub=ClusterApplySolutionTask] [Task, 524] Task:com.vmware.vcIntegrity.lifecycle.ClusterApplySolutionTask ID:52fe11b8-a26d-334e-####-d3791449f3df. Task Failed. Error: Error:
--> com.vmware.vapi.std.errors.error
--> Messages:
--> com.vmware.vcIntegrity.lifecycle.depots.VibDownloadError<Cannot download VIB 'https://hostupdate.vmware.com/software/VUM/PRODUCTION/main/esx/vmw/vib20/native-misc-drivers-esxio/VMware_bootbank_native-misc-drivers-esxio_8.0.3-0.60.24585383.vib'. This might be because of network issues or the specified VIB does NOT exist or does NOT have a proper 'read' privilege set. Make sure the specified VIB exists and is accessible from vCenter Server.

Note: The VIB VMware_bootbank_native-misc-drivers-esxio_8.0.3-0.60.24585383.vib is an example of a driver download that fails.

Environment

VMware vSphere Kubernetes Service
VMware vCenter Server

Cause

The vCenter Server fails to reach the configured depot URLs (such as the legacy hostupdate.vmware.com or custom local repositories), which prevents the vSphere Lifecycle Manager (vLCM) from performing mandatory compliance checks. Because the vSphere Lifecycle Manager cannot validate the host against the desired image, it marks the hosts as incompatible. This state blocks the remediation and installation of the Spherelet VIB required for WCP orchestration.

Resolution

To resolve the orchestration failure, restore connectivity to the vSphere Lifecycle Manager software depots. This action allows vLCM to complete the mandatory compliance checks required for Spherelet VIB remediation.

Update the Patch Setup configuration for the vSphere Lifecycle Manager by correcting the depository URL within the vSphere Client.
Verify that the Supervisor enablement automatically proceeds.
If the enablement process fails to resume, restart the Workload Control Plane (WCP) service on the vCenter Server and monitor the progress.
If the issue persists, engage with Broadcom Support as necessary for further assistance.