VxRail: Failure During 4.x Upgrade Precheck

To prevent upgrade failures due to configuration mismatches or validation errors, always run the VxVerify tool before upgrading VxRail. This validates system health and identifies potential blockers; refer to VxRail: How to Run the VxVerify Tool for details. 

Issue #1:    
One of the ESXi hosts licenses does not support the DRS feature. (Versions earlier than 4.0.300)
Possible solution:    
Likely there are hosts with standard licenses. To resolve this issue, identify those hosts with a standard license and upgrade the license to enterprise level or above.

Issue #2:    
The DRS feature is disabled on the cluster. (Versions earlier than 4.0.300)
Possible solution:    
The upgrade operation can only take place on a cluster with DRS feature enabled. Enable the DRS feature on the cluster and try again.

Issue #3:     
The vCenter Server Appliance has at least one unresolved critical alarm.
Possible Solution:     
Go in to the vSphere client and resolve all critical alarms on the target vCenter Server Appliance.

Issue #4:    
One of the ESXi hosts has at least one unresolved critical alarm.
Possible Solution:     
Go in to the vSphere client and resolve all critical alarms on every ESXi host in the target cluster.

Issue #5:     
The used ESXi hardware platform is not compatible with the used VxRail Manager VIB upgrade bundle included into the composite bundle.
Possible Solution:   
This means that the included VIB bundle is not suitable for being installed on the ESXi hardware platform. To resolve this, go to Dell EMC download site or ACG catalog, and obtain the bundle with matched VIB bundle for your hosts.

Issue #6:    
Pre upgrade hook script execution failure
Possible Solution:   
Confirm that every script that is called in the /usr/lib/vmware-marvin/marvind/webapps/extension/WEB-INF/classes/scripts/pre-upgrade-hook.py is valid and can be executed as a part of the upgrade operation. More details may be found in the lcm.log file.

Issue #7:    
Post upgrade hook script execution failure.
Possible Solution:   
Confirm that every script that is called in the /usr/lib/vmware-marvin/marvind/webapps/extension/WEB-INF/classes/scripts/post-upgrade-hook.py is valid and can be executed as a part of the upgrade operation. More details may be found in the lcm.log file.

Issue #8:   
Unpacked upgrade bundle files were removed from the VSAN data store.
Possible Solution:     
Composite bundle is unpacked into a /bundles directory to the VSAN datastore before the upgrade starts. Try to restart the upgrade operation and verify that the mentioned directory with upgrade bundle files has not been modified when the upgrade process is ongoing.

Issue #9:     
ESXi host in the maintenance mode
Possible Solution:   
Confirm that all ESXi hosts in the target cluster are not in the maintenance mode. Retry the upgrade operation after all ESXi hosts in the cluster are brought out of the maintenance mode.

Issue #10:     
Failed to enter maintenance mode in one of the ESXi hosts in 30 minutes.
Possible Solution:   
Confirm that no VM on the target host has the ISO image mounted into a CD-ROM drive. Unmount if any, and restart the progress.

Issue #11:     
Failed to mount the ISO image for the VCSA upgrade.
Possible Solution:   
Confirm that neither VCSA nor PSC VMs has the ISO image mounted into a CD-ROM drive. Unmount if any, and resume the upgrade process.

Issue #12:   
Failed to upgrade ESRS.
Possible Solution:   
If ESRS is manually deployed, or the ESRS admin password has been changed:   
Option 1) Change the ESRS admin password manually, to be synchronized with VxRail management account.
Option 2) Login ESRS/VE web GUI via https://<ESRS VM IP>:9443 as admin and click upgrade button to upgrade ESRS online.
Option 3) Disable ESRS first and try to finish the VxRail upgrade, then enable ESRS again.

Issue #13:   
Upgrade failure using Active Directory account due to username truncated if VC has AD server as Identity Source.
Workaround:     
When executing upgrade task in VxRail Manager, the window "VxRail Upgrade requires permission to execute" pops up asking for vCSA SSO login and VxRail Manager root account. Use "user@domain" instead of "user@domain.local" for vCSA SSO account to execute the upgrade.

Issue #14:   
The quanta platform is not allowed to upgrade to 7.x.
Possible Solution:   
None

For similar information on other code levels, see: VxRail: Failure During Preupgrade to 4.0 and Later