VxRail:VxRail 7.0.520 或 7.0.521 中的 LCM 显示错误:vSAN 磁盘对象修复超时检索
Summary: 本文介绍从版本 7.0.520 或 7.0.521 升级时 VxRail 生命周期管理 (LCM) 过程失败的问题。它为“vSAN 磁盘对象修复超时”问题提供了解决方案。
This article applies to
This article does not apply to
This article is not tied to any specific product.
Not all product versions are identified in this article.
Symptoms
VxRail LCM 用户界面 vCenter 插件 程序更新 选项卡显示:
Error message: VxRail Update ran into a problem... Failed to retrieve the existing value of the vSAN disk object repair timeout.

在 VxRail Manager 上,单击 /var/log/mystic/lcm-web.log 显示:
2024-09-27T15:19:21.429Z <7ff91b9f32f61676bfb7758d9af41713> lcm [ERROR] <94> ComponentUpgradeService.java performComponentUpgrade() (323): Component VMWARE_ESXI upgrade failed due to Failed to retrieve the existing value of the vSAN disk object repair timeout..
2024-09-27T15:19:21.429Z <7ff91b9f32f61676bfb7758d9af41713> lcm [INFO] <94> LCMServiceImpl.java handleUpgradeException() (1812): handling upgrade exception.
2024-09-27T15:19:21.429Z <7ff91b9f32f61676bfb7758d9af41713> lcm [INFO] <94> LCMServiceImpl.java handleUpgradeException() (1817): Error from vc or node upgrade, sync the composite file
...
2024-09-27T15:19:21.467Z <7ff91b9f32f61676bfb7758d9af41713> lcm [ERROR] <94> LCMServiceImpl.java handleUpgradeException() (1855): failed to upgrade: VXRAIL_COMPOSITE-7.0.531-28777448_for_7.0.x.zip,
with exception:
com.vce.lcm.exception.LCMInternalException: Failed to retrieve the existing value of the vSAN disk object repair timeout.
at com.vce.lcm.core.upgrade.ComponentUpgradeService.performComponentUpgrade(ComponentUpgradeService.java:336)
at com.vce.lcm.api.LCMServiceImpl.performBatchUpgrade(LCMServiceImpl.java:2152)
...
024-09-27T15:19:21.514Z <7ff91b9f32f61676bfb7758d9af41713> lcm [INFO] <94> VirtualApplianceUpgradeParameterStatusHandler.java notifyError() (102): Notify errors for upgrade bundle UpgradeBundleProfile{name='VXRAIL_COMPOSITE-7.0.531-28777448_for_7.0.x.zip', description='null', sizeInKBytes='15664544', bundleFileName='VXRAIL_COMPOSITE-7.0.531-28777448_for_7.0.x.zip', version='7.0.531', build='28777448', targetHardwareInfo='', targetModelInfo='com.vce.commons.vcm.state.CompositeManifestFile$TargetModelInfo@3901ec9', replaceTargetInfo='com.vce.commons.vcm.state.CompositeManifestFile$ReplaceTargetInfo@16a5c26c', targetNicModelInfo='com.vce.commons.vcm.state.CompositeManifestFile$TargetNicModelInfo@2949e0b9', removeUpgradeVIB='false', forceInstall='false', skipList='[]', upgradeTime='0', rebootFlag='false', isUpgradeComponent='false', totalEstimated='100668', totalUsed='54511', minimumVxRailVersion='7.0.010', patchType=''}, upgradeStep UPGRADE, upgradeTarget UpgradeTarget{ComponentType=VXRAIL_COMPOSITE, name='esxxxx.domain.country', isPipelineTask='false'}, action Retrieve the value of the vSAN disk object repair timeout., message Failed to retrieve the existing value of the vSAN disk object repair timeout.
额外的错误详细信息有助于识别受影响的主机和其他症状 过多的未完成作:
2024-09-27T15:18:29.011Z <7ff91b9f32f61676bfb7758d9af41713> lcm [INFO] <374> BatchUpgrade.java updateVsanClomTimeoutValueBeforeUpgrade() (881): Obtaining the existing vSAN Clom timeout value for th
e host : esxxxx.domain.country
...
2024-09-27T15:18:33.070Z <7ff91b9f32f61676bfb7758d9af41713> lcm [WARN] <374> ScriptServiceImpl.java runLocalScript() (507): [/etc/vmware-marvin/scripts/lcm/scripts/update-vsan-clom-repair-timeout.p
y@localhost]: <stderr> Traceback (most recent call last):
File "/usr/lib/vmware-marvin/marvind/temp/3741351928508979296.tmp", line 154, in <module>
main()
File "/usr/lib/vmware-marvin/marvind/temp/3741351928508979296.tmp", line 149, in main
get_timeout_value(options)
File "/usr/lib/vmware-marvin/marvind/temp/3741351928508979296.tmp", line 133, in get_timeout_value
result = advanced_sys_settings.List(False, VSAN_PROPERTY)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/lib/python3.11/site-packages/pyVmomi/VmomiSupport.py", line 706, in <lambda>
self.f(*(self.args + (obj,) + args), **kwargs)
File "/usr/lib/python3.11/site-packages/pyVmomi/VmomiSupport.py", line 512, in _InvokeMethod
return self._stub.InvokeMethod(self, info, args)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/lib/python3.11/site-packages/pyVmomi/ManagedMethodExecutorHelper.py", line 74, in InvokeMethod
result = self.mme.ExecuteSoap(moid=moid,
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/lib/python3.11/site-packages/pyVmomi/VmomiSupport.py", line 706, in <lambda>
self.f(*(self.args + (obj,) + args), **kwargs)
File "/usr/lib/python3.11/site-packages/pyVmomi/VmomiSupport.py", line 512, in _InvokeMethod
return self._stub.InvokeMethod(self, info, args)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/lib/python3.11/site-packages/pyVmomi/SoapAdapter.py", line 1397, in InvokeMethod
raise obj # pylint: disable-msg=E0702
^^^^^^^^^
pyVmomi.VmomiSupport.vmodl.fault.SystemError: (vmodl.fault.SystemError) {
dynamicType = <unset>,
dynamicProperty = (vmodl.DynamicProperty) [],
msg = 'A general system error occurred: Too many outstanding operations',
faultCause = <unset>,
faultMessage = (vmodl.LocalizableMessage) [],
reason = 'Too many outstanding operations'
}Cause
VxRail 版本 7.0.520 和 7.0.521 中的代码问题导致 esxcli 主机命令随时间推移卡住。日志中的查询返回:
reason = 'Too many outstanding operations'
这会导致 LCM 故障,升级过程无法通过以下方式检索 VSAN 配置值 esxcli。
提醒:此问题仅出现在上述配置了安全连接网关的发布版本上的 VxRail 群集上。
Resolution
此问题的永久修复已在 VxRail 版本 7.0.531 中提供。发行说明位于 Dell VxRail 7.0.x 发行说明 |Dell US (需要客户登录)
用户必须重新启动 hostd management service 在重新启动 VxRail LCM 升级脚本之前,在故障节点上。这将清除未完成的请求并允许升级继续。
/etc/init.d/hostd restart
有关重新启动 ESXi hostd service,请参阅 Broadcom 文章 重新启动 ESXi 中的管理代理程序。
如果需要帮助,请查看日志、识别受影响的主机或重新启动服务,请联系 戴尔支持。
Additional Information
如果已应用 STIG ,请查看文章 VxRail:在使用 STIG 升级到 7.0.400 期间,某些库的文件权限不正确,这是导致此错误的潜在原因
Affected Products
VxRail, VxRail Appliance Series, VxRail SoftwareArticle Properties
Article Number: 000230587
Article Type: Solution
Last Modified: 17 Nov 2025
Version: 7
Find answers to your questions from other Dell users
Support Services
Check if your device is covered by Support Services.