VCF - Upgrade/Migration from vSphere 7.x to 8.x fails in SDDC Manager at POSTCHECK stage

Products

• VMware SDDC Manager

Issue/Introduction

When upgrading VMware Cloud Foundation Workload Domain from 4.x to 5.x, the vCenter will make a migration upgrade from vSphere 7.x to 8.x

Errors can be found in the upgrade log:

XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXX: Upgrade: postInstallUpgrade: postInstallUpgrade executed successfully,
XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXX: Successfully ran upgrade stage VCENTER_UPGRADE_POST_INSTALL,
XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXX: Upgrade element resourceType: VCENTER resourceId: XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXX recorded stage VCENTER_UPGRADE_POST_VALIDATION,
XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXX: Post-validation of the VCenter version successful,
XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXX: Upgrade precheck started for health check.,
XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXX: Post-validation of the VCenter health status successful,
XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXX: Upgrade: cleanup: cleanup executed successfully,
XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXX: Upgrade element resourceType: VCENTER resourceId: XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXX status changed to COMPLETED_WITH_FAILURE,
XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXX : COMPLETED_WITH_FAILURE

 

This upgrade will require a target appliance to be created, then the source VM will be shut down, and the target appliance will start.

If all services start, the target appliance is renamed. After this, the upgrade is complete, and post checks are run on SDDC Manager

SDDC Manager UI shows an older version of vCenter:

Environment

VAMI will show the proper version.

Tasks on vCenter will show that the currently used vCenter VM is the target appliance.

 

Cause

Postchecks from the SDDC Manager can fail due to timeout or the time it takes to update the LCM task. There is no functionality loss on the vCenter itself.

Resolution

Important Note: Ensure you have taken a snapshot of the SDDC Manager VM before proceeding with the steps below.

Update the PSQL database on SDDC Manager either manually or use the Async Patch tool-sync option to complete the task:

/usr/pgsql/13/bin/psql -U postgres -h localhost -d platform -c "select id, vm_name, version from vcenter;"

/usr/pgsql/13/bin/psql -U postgres -h localhost -d platform -c "update vcenter set version='<version from VAMI>' where vm_name='vCenter name';