VMware

vCenter 6.7 U3 to vCenter 7.0 Upgrade Falters at Pre-Check with Internal Error

Troubleshooting an Embedded vCenter Upgrade: A Real-Life Case Study

As a VMware consultant, I have encountered numerous challenges during embedded vCenter upgrades. Recently, one of my customers experienced an issue while attempting to upgrade their vCenter from 6.7U3 to 7.0. The upgrade process failed during Stage 2, specifically when performing a pre-check. After investigating the requirements-upgrade-runner.log file, we found an error message that read “lookup.fault.EntryNotFoundFault.”

We started troubleshooting by reviewing the requirements-upgrade-runner.log file and searching for any relevant information that might indicate an issue with the vCenter Server. However, the logs were inconclusive, and we couldn’t find anything that would point to a specific problem. The customer raised a support request with VMware GSS, and after exchanging several puzzled inquiries and log bundles, it was escalated to engineering for further investigation.

While waiting for the resolution from VMware, we decided to explore other possible causes of the issue. During our investigation, we found an interesting error message: “Cluster HA Error.” This message led us to a VMware KB article (KB 76584) that described a scenario where the embedded PSC services might be in read-only mode, preventing several core vCenter activities from functioning properly.

As the ‘LookupService’ is a core service in the PSC and is being interrogated (and probably updated) by the vCenter upgrade wizard, we asked the customer to check the state of the embedded PSC. To our surprise, the PSC was in read-only mode. Following the KB article, we set the PSC back to active mode, and the upgrade process succeeded without any issues.

The lessons learned from this case study are:

1. Always review the requirements-upgrade-runner.log file carefully during an embedded vCenter upgrade, as it may contain valuable information about the issue.

2. Be aware of the possibility of the embedded PSC services being in read-only mode and causing issues with the upgrade process.

3. Check the state of the embedded PSC before attempting the upgrade, and make sure it is set to active mode.

4. Escalate any issues or errors to VMware GSS, as they may be able to provide additional insight or resolutions.

In conclusion, this case study highlights the importance of thorough troubleshooting during embedded vCenter upgrades. By carefully reviewing log files and exploring all possible causes of an issue, consultants can help customers resolve problems and ensure a successful upgrade process. Additionally, being aware of potential issues such as the PSC being in read-only mode can save time and effort in resolving the problem.