Summary: This article details how to resolve a failed upgrade that is failing with the error: Failed to pre-check virtual machine VMware vCenter Server Appliance meets upgrade requirements, due to the cluster's current vCenter deployment size being too small for its existing inventory.
Article Content
| Issue | Scenario#1 An upgrade from 4.5.x to 4.5.x (could possible also apply to 4.0.x to 4.5.x upgrades) fails during the deployment of the 6.7 vCSA with: Failed to pre-check virtual machine VMware vCenter Server Appliance meets upgrade requirements. The VxRail Manager's /var/log/mystic/lcm.log and the original vCenter's /var/log/vmware/upgrade/requirements-upgrade-runner.log contain errors similar to the below (the bold text is the key): 2019-06-18T19:48:01.76Z INFO upgrade_commands Determining source and target deployment sizes. 2019-06-18T19:48:01.77Z INFO upgrade_commands Target deployment size is small 2019-06-18T19:48:01.77Z INFO upgrade_commands Source deployment size is medium 2019-06-18T19:48:01.78Z ERROR upgrade_commands Target compute resources are insufficient for the source inventory 2019-06-18T19:48:01.78Z INFO upgrade_commands Recommended minimum OVF profile is 'medium'. 2019-06-18T19:48:01.79Z INFO upgrade_commands Validating preupgrade disk requirements will fit in the target's disk partitions. 2019-06-18T19:48:01.92Z INFO common /bin/df command completed with exit code 0 2019-06-18T19:48:01.98Z INFO common /bin/df command completed with exit code 0 2019-06-18T19:48:01.99Z INFO upgrade_commands Destination import disk set to 'seat'. 2019-06-18T19:48:01.99Z INFO upgrade_commands Deployment autoconfig parameter is set to: True. 2019-06-18T19:48:01.99Z INFO upgrade_commands Target disks sizes are sufficient. 2019-06-18T19:48:01.99Z ERROR upgrade_commands Current deployment size is too small for the existing inventory. Scenario#2 An upgrade from 4.5.x to 4.7.x fails during the deployment of the 6.7 vCSA with: Failed to pre-check virtual machine VMware vCenter Server Appliance meets upgrade requirements. The VxRail Manager's /var/log/mystic/lcm.log 2019-07-30T09:53:53.923+0000 ERROR [pool-10-thread-1] com.vce.lcm.service.LCMServiceImpl LCMServiceImpl.handleUpgradeException:1569 - failed to upgrade: VXRAIL_COMPOSITE-4.7.211-13893930_for_4.5.x.zip, with exception:com.vce.lcm.exception.LCMInternalException: Failed to pre-check virtual machine VMware vCenter Server Appliance (bEwvyQx) meets upgrade requireme nts.Caused by: java.util.concurrent.ExecutionException: com.vce.lcm.exception.LCMInternalException: Failed to pre-check virtual machine VMware vCenter Server Appliance (bEwvyQx) meets upgrade requirements. The original and target vCenter's /var/log/vmware/upgrade/requirements-upgrade-runner.log contain errors similar to the below (the bold text is the key): 'requirementMismatchSpecs': [{'severity': 'ERROR', 'problemId': None, 'description': None, 'resolution': {'localized': 'Host profiles with versions lower than 6.0.0 are not supported by vCenter Server 6.7. Upgrade the 1 host profiles listed below to version 6.0.0 or later before proceeding with the upgrade of vCenter Server. \nUpgrade the host profiles before upgrading all hosts with versions lower than 6.0.0. For more information see Knowledge Base article 52932. \n\nList of unsupported host profiles:\n \n Host Profile. \n', 'args''\n Host Profile. \n'], 'id':'vcdb.resolution.hostprofile.version.linux', 'translatable': 'Host profiles with versions lower than 6.0.0 are not sed by vCenter Server 6.7. Upgrade the %(0)s host profiles listed below to version 6.0.0 or later before proceeding with the upgrade of vCenter Server. \nUpgrade the host profiles before upgrading all hosts with versions lower than 6.0.0. For more information see Knowledge Base article 52932. \n\nList of unsupported host profiles:\n %(1)s'}, 'text': {'localized': 'Source vCenter Server has unsupported version of host profiles.', 'id': 'vcdb.error.hostprofile.version.linux', 'translatable': 'Source vCenter Server has unsupported version of host profiles.'}}], 'extraArguments': {'src.db.type': 'embedded'}, The message in vcdb_req.err ERROR: invalid-hostprofile-version -> 1 {HostProfile: Host Profile, Version: 5.5.0} ERROR: invalid-hostprofile-version-count -> 1 vcdb_req.err (END) |
| Cause | Scenario#1 A VxRail Manager deploys a "small" vCenter. Each size of vCenter has specific VM hardware specifications (vCPU, Memory, and Storage capacity) and limitations in expected capacity (for example, a small vCSA is supposed to host 1000 or less virtual machines). The VxRail LCM upgrade script checks the existing vCSA's virtual hardware settings and determine which size of new vCSA to deploy. If the deployment size of the new vCSA is insufficient for what the current vCSA contains (for example, if the original vCSA contains 1001+ VMs), the pre-check will fail and the VxRail LCM upgrade will fail with the above error. Scenario#2 Host Profile version at 5.5 is not supported by VC 6.7 |
| Resolution | Scenario#1 -The 6.7 vCSA will need to be powered off and the original vCSA will need to be modified. -There are two options for how to proceed: Option 1: -Leave the 6.7 PSC running. -Power off the 6.5 vCSA (the 6.7 vCSA was powered off in the previous step). -Reference the below Medium vCSA Hardware Configuration Chart to re-size the 6.5 vCSA's hardware configuration (CPU, Memory, and Hard Disks). *Note: Updating the hard disk sizes cannot be done while there are snapshots of the VM. Therefore, any snapshots of the vCSA will need to be deleted prior to updating the Hard disk sizes. If the VM has any snapshots, re-sizing the disks will result in a failure for something similar to: "Failed to reconfigure virtual machine VMware vCenter Server Appliance. Invalid operation for device '4'." -Power on the 6.5 vCSA and follow https://kb.vmware.com/s/article/2145603 to expand vCenter's disks via CLI. -Confirm that you can log into vCenter and the VxRail Manager. -Take a snapshot of the 6.5 vCSA. -Click the "Retry" button to start the upgrade again. Option 2: -Power off the 6.7 PSC and 6.5 vCSA (the 6.7 vCSA was powered off in the previous step) -Power on the 6.5 PSC and wait for all of its services to start. Note: This can be monitored via the PSC's CLI with the below command: service-control --status - Power on the 6.5 vCSA and wait for all of its services to start. Note: This can be monitored via the PSC's CLI with the below command: service-control --status -Optional: Revert the service VMs (VxRail Manager, PSC, and vCSA) to their pre-upgrade snapshots -Log into the VAMI of both the PSC and vCSA as root to confirm there are no hung upgrade processes (if the VAMI pages look normal, there is no upgrade process running). -Power off the 6.5 vCSA. -Reference the below Medium vCSA Hardware Configuration Chart to re-size the 6.5 vCSA's hardware configuration (CPU, Memory, and Hard Disks). *Note: Updating the hard disk sizes cannot be done while there are snapshots of the VM. Therefore, any snapshots of the vCSA will need to be deleted prior to updating the Hard disk sizes. If the VM has any snapshots, re-sizing the disks will result in a failure for something similar to: "Failed to reconfigure virtual machine VMware vCenter Server Appliance. Invalid operation for device '4'." -Power on the 6.5 vCSA and follow https://kb.vmware.com/s/article/2145603 to expand vCenter's disks via CLI. -Confirm that you can log into vCenter and the VxRail Manager. -Take a snapshot of the 6.5 vCSA. -Start the VxRail upgrade via the VxRail Manager web GUI. Medium vCSA Hardware Configuration Chart:  Scenario#2 Since host profile feature is not supported in vxrail per https://support.emc.com/kb/529223, delete the host profile in original vcsa. Then retry upgrade and passed the failed point. Home > Policies and Profiles > choose host profile > actions : delete  |