lcm.2025-xx-xx.0.log.gz: data = com.vmware.esx.settings.clusters.software.drafts.validate_result => {notifications=com.vmware.esx.settings.notifications => {warnings=[], errors=[com.vmware.esx.settings.notification => {retriable=<unset>, id=com.vmware.vcIntegrity.lifecycle.EsxImage.SolutionComponentNotFound, originator=<unset>, time=2025-xx-xxT12:29:19.174Z, message=com.vmware.vapi.std.localizable_message => {args=[nsx-lcp-bundle, VMware NSX-T], default_message=Component(s) nsx-lcp-bundle within software Solution VMware NSX-T cannot be found in depot., localized=<unset>, id=com.vmware.vcIntegrity.lifecycle.EsxImage.SolutionComponentNotFound, params=<unset>}, type=<unset>, resolution=<unset>}], info=[]}},
lcm.2025-xx-xx.0.log.gz:com.vmware.xxx.sddc.lcm.model.error.LcmException: Unable to set NSX solution to desired state spec. Component(s) nsx-lcp-bundle within software Solution VMware NSX-T cannot be found in depot. Image is not valid.
VCF 5.x
NSX/vDefend 4.2.2 and above with Turbo mode
During vLCM cluster preparation, the "nsx-scx-vlcm-bundle" was correctly set in the desired state. However, during the upgrade, the SDDC Manager workflow is attempting to set the non-scx bundle "nsx-lcp-bundle" to the desired state instead. This discrepancy is causing the component clash.
This issue is fixed in VCF 5.2.3
If upgrade is NOT an option
Perform ESXi Upgrade outside the SDDC Workflow
PR 3631740