vLCM uploaded Components are not visible when you create image
Article ID: 412308
Updated On:
Products
Issue/Introduction
After manually uploading NSX LCP and Spherelet components to vLCM components are not available to be selected when creating new image.
You don't have NSX or Supervisor enabled on cluster level.
In vCenter logs you see following
/var/log/vmware/vmware-updatemgr/vum-server/vmware-vum-server.log
"display_name": "ESXi K8s node agent",
--> "display_name": "ESXi K8s node agent",
--> "ESXi K8s node agent"
--> "default_message": "Components ESXi K8s node agent are removed in the image. They will be removed from the host during remediation.",
--> "key": "nsx-lcp-bundle",
--> "display_name": "NSX LCP Bundle",
--> "OPTIONAL": "NSX LCP Bundle(#########)"
--> "NSX LCP Bundle"
--> "default_message": "Components NSX LCP Bundle are removed in the image. They will be removed from the host during remediation.",
--> "key": "nsx-lcp-bundle",
Environment
vSphere 8.x
Cause
Both products NSX and Supervisor needs to be enabled on cluster for vLCM to be able to managed them.
More information can be found in
Resetting the VMware Update Manager Database
"The NSX depot gets uploaded to vCenter when NSX is configured on a vLCM cluster only if the depot is not already present. So, if the reset-db script removes this depot from vCenter, then this depot can be uploaded again by creating an empty vLCM cluster and enabling NSX on that cluster."
and in
Enable vSphere Supervisor on a Cluster Managed by vSphere Lifecycle Manager
"To run Kubernetes workloads, you can enable vSphere Supervisor on a cluster that you manage with a single vSphere Lifecycle Manager image. After it is enabled, you can manage the Supervisor using vSphere Lifecycle Manager."
Resolution
Enabling NSX and Supervisor on cluster level
Feedback
