VxRail: vSAN ESA Cluster Upgrade Failed

When upgrading a vSAN ESA cluster from 8.0.361 to 8.0.380, the upgrade fails on the first host.

The upgrades for the VxRail manager and vCenter succeed.

lcm-web.log shows:

2026-05-22T02:01:32.775Z <2fa9ab11f1a1ef2fe6136f2337ebcd5c> lcm [WARN] <1051> ScriptServiceImpl.java waitingForResponse() (563): [/etc/vmware-marvin/scripts/lcm/scripts/update-vsan-clom-repair-timeout.py@localhost]: <stderr> Traceback (most recent call last):
  File "/usr/lib/vmware-marvin/marvind/temp/17819806287846384705.tmp", line 13, in <module>
    from pyVmomi import DynamicTypeManagerHelper, vim
  File "/usr/local/lib/python3.11/site-packages/pyVmomi/DynamicTypeManagerHelper.py", line 22, in <module>
    from Cache import Cache
ModuleNotFoundError: No module named 'Cache'

The vSAN ESA cluster only supports vLCM upgrade mode. This issue occurs when the current cluster is still using LCM upgrade mode.

Run "esxcli vsan cluster get" to confirm if the cluster is using OSA or ESA mode.

vSAN Health Service - Cluster health - vSphere Lifecycle Manager (vLCM) configuration

1. Enable vLCM mode from the VxRail plug-in.
2. Cancel the upgrade.
3. Upload the upgrade bundle.
4. Retry the upgrade.

For information about enabling vLCM, see: VxRail: How to enable vSphere Lifecycle Manager mode