vCenter 8.0 upgrade issue and fixes.
- Content library service was failing in the firstboot start phase.
The error is pointing out to Content library, from the logs we verified that the cl_metadata table is corrupt.
Solution Recommendation : Edited the vCenter Database, changed the cl_metadata table.
Made changes to the table as follows :
database.schema.version | [ “1.0.0”, “1.0.12”, “1.0.24”, “1.0.44”, “5.0.0” ]
2. Deploying the temp instance the network was not available.
Solution Recommendation :
- Created a new standard switch
- created the related kernel port
- create new port group
- Now the network was listed in the deployment page
- selected this port group during the installation
- later edited the NIC for the temp VM and changed to DV switch.
3. vCenter Server has extensions registered that are unsupported by the new vCenter Server. Extensions: NSX Manager (by VMware)
Solution Recommendation : Uninstalled the NSX Plugin
4. TRUSTED_ROOTS has weak signature algorithm sha1WithRSAEncryption.Required with a certificate that uses the SHA-2 signature algorithm.
Solution Recommendation : SHA1 is not supported in vSphere 8.x. Stale entry removal is required as replication partners have to be in a healthy status for upgrade.
5. VMDir Replication between partners is not working.
Solution Recommendation : Due to the Linked mode state with the old retired VC, unregistered the old VC from the upgrade VC.
5. Host profiles with versions lower than 6.7 are not supported by vCenter Server 8.0.0. Upgrade.
Solution Recommendation : Upgrade the host profle.