VAMI page https://VCSA-FQDN:5480/configurev2/#/ timeout during stage 2 of the vCenter upgrade

Products

• VMware vCenter Server

Issue/Introduction

• At stage 2 of the vCenter upgrade, the VAMI page at URL: https://VCSA-FQDN:5480/configurev2/#/ gets timed out.
  
  
  
  
• In the /var/log/vmware/upgrade/import-upgrade-runer.log file of the vCenter, entries similar to below are seen:
YYYY-MM-DDTHH:MM:SS INFO UpgradeRunner Persisting upgrade workflow context ..
YYYY-MM-DDTHH:MM:SS INFO deployer.migration env deployer Cleaning-up migration environment ...
YYYY-MM-DDTHH:MM:SS INFO deployer.migration env deployer All targets were already unregistered as extensions
YYYY-MM-DDTHH:MM:SS INFO deployer.migration_env_deployer Cleaning up target: None target with address=XXX.X.X.X
YYYY-MM-DDTHH:MM:SS INFO UpgradeRunner Upgrade mode 'import' completed successfully
YYYY-MM-DDTHH:MM:SS INFO root Exiting with exit-code 0
  
  
• In the /var/log/vmware/upgrade/postupgrade.log file of the vCenter, entries similar to below are seen:
  YYYY-MM-DDTHH:MM:SS INFO
YYYY-MM-DDTHH:MM:SS INFO base_commands Executing command -- ['/uar/bin/python3', '/uar/lib/vmware/cis_upgrade_runner/UpgradeOrchestrator.py', '-m', 'import', '-f', 'upgrade-import-config.json', '-o', '/var/log/vmware/upgrade/import. json', ' -- logDir', '/var/log/vmware/upgrade', ' -- logFileName', 'import-upgrade-runner. log', ' -- cancelFile', '/var/tmp/upgrade_cancel. op', '-1', 'en', ' -- logLevel', 'INFO', ' -- silent', ' -- disableScreenLog'] on localhost
YYYY-MM-DDTHH:MM:SS INFO main SUCCESS: Upgrade IMPORT completes successfully
YYYY-MM-DDTHH:MM:SS INFO root Exiting with exit-code 0

Environment

• vCenter 7.x
• vCenter 8.x

Cause

This is an expected behavior when the vCenter services restarts during the update process, causing the VAMI page to timeout and this does not indicate an issue.

Resolution

1. Post the vCenter upgrade, wait until vCenter services are up before bringing up the vCenter UI.
2. Connect to the vCenter appliance via SSH and use the following command to check vCenter service status:
   • service-control --status --all
3. After confirming vCenter services are up, refresh the browser and open the vCenter client.
4. Confirm the status and version of vCenter from VAMI and vCenter UI.