vmware-vum-server.log, there is entry in the component and solution as well. In solutions, it is the latest version that is being used, in component it will be the old version.{
--> "add_on": null,
--> "alternative_images": null,
--> "base_image": {
--> "version": "8.0.3-0.79.24859861"
--> },
--> "components": {
--> "nsx-lcp-bundle": "4.2.1.3.0-8.0.24533885",
--> },
--> "solutions": {
--> "com.vmware.nsxt": {
--> "components": [
--> {
--> "component": "nsx-lcp-bundle"
--> }
--> ],
--> "version": "4.2.3.3.0-25171319"
--> },
VMware vCenter Server 8.x
This issue typically occurs because certain components were inadvertently reclassified as user-managed components during the deployment of a new solution. In this specific instance, the issue impacted the NSX bundle configurations.
The component needs to be removed from the desired image. Below are the steps:
Get the desired image of the cluster and check nsx-lcp-bundle in the component section:
dcli com vmware esx settings clusters software get --cluster <cluster moid>
Create the draft:
dcli com vmware esx settings clusters software drafts create --cluster <moid>
The output is the draft id
Delete the component:
dcli com vmware esx settings clusters software drafts software components delete --cluster <cluster moid> --draft <draft id> --component nsx-lcp-bundle
Commit the draft:
dcli com vmware esx settings clusters software drafts software commit-task --cluster <cluster moid> --draft <draft id> The output is commit task id
Monitor the commit task:
dcli com vmware cis tasks get --task <task id>
Once the commit task has finished successfully, verify the desired image to ensure the offending component has been removed.
dcli com vmware esx settings clusters software get --cluster <cluster moid>
On vCenter UI, will see compliance check succeeds.