If you are upgrading a workload domain that uses vSphere Lifecycle Manager images and its cluster image was created from an ESXi host that uses vSphere Lifecycle Manager baselines, then NSX host cluster upgrade will fail. A cluster image created from an ESXi host that uses vSphere Lifecycle Manager baselines contains an NSX component that causes this issue.
VMware Cloud Foundation 5.2
When solutions like HA/NSX/WCP are enabled in a Baseline Cluster and user tries to seed the image from a host in the Baseline Cluster, then host seeding will consider these solutions as normal Components rather than Solutions, because solution related metadata is not available in a Baseline Cluster as Solutions is a vLCM concept. If a cluster is created with such image and NSX upgrade is performed on hosts of that cluster, upgrade fails due to conflicting nsx-lcp-bundle.
Issue resolved in ESXi and vCenter 8.0U3 or later
Workaround:
Do not create cluster images from an ESXi host that uses vSphere Lifecycle Manager baselines. If you encounter this issue, you can resolve it by using the vSphere Client to remove the NSX LCP Bundle component from the cluster image. This change is a per cluster change and needs to be done for every cluster in an affected SDDC manager environment.
Here are the steps:
1. Log in to vSphere Client
2. Navigate to affected cluster
3. Select "Updates" tab
4. Export cluster image as JSON
5. Edit JSON file
6. Replace "components" section with "components": null,
7. Save modified JSON
8. Import modified JSON
9. Verify and save updated cluster image
10. Retry NSX upgrade in SDDC Manager