Symptoms
VxRail upgrade fails due to timeout during entering maintenance mode.
Cause
In some production environments, a host may have a super-sized VM and or one with a heavy work load. Entering Maintenance Mode on this host could time out after 30 minutes. This will cause an upgrade failure.
Resolution
To workaround this issue change the timeout in lcm-application.properties :
- SSH login VxRail Manager as Mystic.
- Change to "root" user. su.
- Edit the lcm-application.properties
- Path in 4.5 train: /usr/lib/vmware-marvin/marvind/webapps/extension/WEB-INF/classes/lcm-application.properties
- Path in 4.7 train: /usr/lib/vmware-marvin/marvind/webapps/ROOT/WEB-INF/classes/lcm-application.properties
- Path in 7.0 train change the parameter in both files below: In 7.0 train, lcm loads the parameters from lcm folder first, and then load the parameters from ROOT folder. If there are same keys, the values will be overwritten.
- /usr/lib/vmware-marvin/marvind/webapps/ROOT/WEB-INF/classes/lcm-application.properties
- /usr/lib/vmware-marvin/marvind/webapps/lcm/WEB-INF/classes/lcm-application.properties
- Change the value to "3600" - which means a 60 min timeout for entering Maintenance Mode.
# The timeout for enter maintenance mode
lcmProperties.enter.maitenance.mode.timeout=1800