When performing out-of-band (OOB) upgrades on ESXi hosts outside of the Lifecycle Management (LCM) workflow, the SDDC Manager inventory database may fail to synchronize, causing the user interface to display older build versions
SDDC Manager maintains its own inventory database of host versions. When an ESXi host is upgraded outside of the SDDC Manager lifecycle management workflow (out-of-band upgrade), the inventory database is not automatically updated. This causes the SDDC Manager UI to display the old version even though the host is running the new version.
Before making any changes, make sure to take a snapshot of the SDDC VM Taking and restoring snapshots of the SDDC Manager appliance
To resolve the issue, manual synchronization of the SDDC Manager inventory database.
root user and run vmware -v to confirm the actual build version.vcf user and switch to root usercurl -s localhost/inventory/hosts | jq -r '.[]|{id,hostName}'/usr/pgsql/13/bin/psql -U postgres -h localhost -d platformSELECT id, hostname, version FROM host;\qcurl -X PATCH 'localhost/inventory/entities/<host-id>' \ -d '{"version":"<version>", "type":"ESXI"}' \ -H 'Content-Type:application/json'<version> with the correct ESXi version retrieved from Step 1 - it will be in the format of eg: 8.0.3-####### and <host-id> should be replaced with the UUID retried from step 3)/opt/vmware/vcf/operationsmanager/scripts/cli/sddcmanager_restart_services.shNote: To avoid future version discrepancies, prioritize the use of SDDC Manager Lifecycle Management for all ESXi host upgrades.
Synchronize inventory versions after out-of-band upgrade in a VMware Cloud Foundation Environment