Skip to main content
  • Place orders quickly and easily
  • View orders and track your shipping status
  • Enjoy members-only rewards and discounts
  • Create and access a list of your products
  • Manage your Dell EMC sites, products, and product-level contacts using Company Administration.

Article Number: 000170028


VxRail: Failure during 4.x upgrade pre-check

Summary: How to troubleshoot VxRail during a 4-x pre-check upgrade.

Article Content


Symptoms

There may be multiple scenarios that caused this error message. Refer to Resolution section for possible issues and corresponding solutions.

Cause

The internal service errors for the offline upload operation failure may be one of the following: 

Resolution

Issue #1:    
One of the ESXi hosts licenses does not support 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 alarms.
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 alarms.
Possible Solution:     
Go in to the vSphere client and resolve all critical alarms on every ESXi host in the target cluster.

Issue #5:     
Used ESXi hardware platform is not compatible with used VxRail Manager VIB upgrade bundle included into the composite bundle.
Possible Solution:   
This means 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 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 host 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 ESRS admin password has been changed:   
O
ption 1) Change ESRS admin password manually, to be in sync with VxRail management account.
O
ption 2) Log in 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 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, window "VxRail Upgrade requires permission to execute" pops up asking for vCSA SSO log in and VxRail Manager root account. Use "user@domain" instead of "user@domain.local" for vCSA SSO account to execute the upgrade.

Issue #14:   
Quanta platform is not allowed to upgrade to 7.x.

Possible Solution:   
None.

Article Properties


Product

VxRail 460 and 470 Nodes, VxRail Appliance Family, VxRail Appliance Series

Last Published Date

10 May 2021

Version

3

Article Type

Solution