VMware Cloud Community
chenjed1
Contributor
Contributor

Upgrade from VCenter 6.0 to VCSA 6.5 or 6.7 failing

Upgrade failing on new appliance, no error message but is stuck forever as per image. Thrice this happening

0 Kudos
4 Replies
navina
Enthusiast
Enthusiast

But are you able to access the vCenter via the IP / FQDN?

Suspecting the upgrade page is stuck

Regards,
Navin A
0 Kudos
drdoc_fred
Enthusiast
Enthusiast

The upgrade from VCenter 6.0 to VCSA 6.5 or 6.7 could be failing due to several reasons. Here are some potential causes and their solutions:

  1. The vCenter OS password (root password) might be expired. You need to ensure that the root password is not expired.

  2. There could be an issue with the 'scafirstboot' service during the upgrade. You might see errors in the firstbootStatus.json file or the scafirstboot.py_####_stderr.log file. You can refer to the document 'Understanding and Troubleshooting vCenter Server and vCenter Server Appliance 6.7 Firstboot Install/Deployment, Upgrade, or Migration Failures' for more information.

  3. The upgrade might fail if the vCenter Single Sign-On certificate does not contain any IP address entries within the Subject Alternative Name.

  4. If the upgrade process is stuck at 70%, it might be due to an issue with the Virtual Appliance Management Interface (VAMI). The VAMI update status might be stuck at the step [Started] Update Packages.

  5. There could be an issue with the vCenter Server database. You might see an error message 'Internal error occurs during VMWARE vCenter Server Database pre-upgrade checks'.

  6. The upgrade might fail if there are issues with the 'Auto Deploy' service. You might see an error message 'Failed to register Auto Deploy'.

  7. There could be an issue with the vCenter Server Appliance upgrade process. You might see an error message 'Unable to contact the source vCenter'.

0 Kudos
chenjed1
Contributor
Contributor

Yes it opens by IP, i can SSH also to it

0 Kudos
chenjed1
Contributor
Contributor

Root passwords fine not expired, the VCSA accessible by IP etc after it shuts down the former vCenter. It just gets stuck at 85% stage 2 as per image showing starting VSAN Health service. Even if you SSH and start these services it wont proceed and throws no error on the screen

0 Kudos