Loading...
Loading...
The VxRail upgrade may fail with a message in the UI similar to: Failure occurred while scheduling firmware From the VxRail Manager LCM upgrade log /var/log/mystic/lcm-web.log, Precheck for DUP existence is seen as failed: 2023-06-30 19:57:45,921 INFO [LCM] [lcm-node-0] c.v.c.c.v.PlatformServiceDOClient [PlatformServiceDOClient.java:156] Platform Service DO Enabled on host: *****, true 2023-06-30 19:57:45,927 INFO [LCM] [lcm-node-0] c.d.v.l.d.p.r.d.HostDO [HostDO.java:611] Query Host Do Task: b32ce6dd-dc7c-4291-aff0-08a59f145280, response: {"task_id": "b32ce6dd-dc7c-4291-aff0-08a59f145280", "state": "FAILURE", "error": {"code": "", "message": "Pre-check for DUP existence failed." , "params": []}, "result": {"task_id": "TID00000011", "status": "ERROR", "detail": {"status": "ERROR", "message": "Pre-check for DUP existence failed." , "os_reboot_required": false, "summary": [{"dup_name": "Fibre-Channel_Firmware_KV0M6_WN64_15.35.08_A00-00.EXE", "type": "", "status": "ERROR", "message_id": "PSERR0006", "message": "This DUP file does not exist on host: /vmfs/volumes/VxRail-vSAN/upgradeBundles/Fibre-Channel_Firmware_KV0M6_WN64_15.35.08_A00-00.EXE" , "percent_complete": null, "supported_components": []}]}, "start_time": "2023-06-30T19:53:35", "finish_time": "2023-06-30T19:57:09", "executor": "LINZHI"}}2023-06-30 19:57:45,929 INFO [LCM] [lcm-node-0] c.e.m.m.e.DynamicReloadableResourceBundleMessageSource [DynamicReloadableResourceBundleMessageSource.java:17] Try to translate message: Failure occurred while scheduling firmware. The error message: FAILURE. 2023-06-30 19:57:45,930 INFO [LCM] [lcm-node-0] c.e.m.m.e.DynamicReloadableResourceBundleMessageSource [DynamicReloadableResourceBundleMessageSource.java:19] Succeeded to translate message: Failure occurred while scheduling firmware. The error message: FAILURE. -> Failure occurred while scheduling firmware. The error message: FAILURE .
A change in the working location of the VxRail LCM upgrade components has caused this issue. There is an exception causing it to look for the file in the old location. Firmware in recent 7.0 codes: Old Location: /vmfs/volumes/<VSAN datastore>/upgradeBundles/ New Location: /vmfs/volumes/<VSAN datastore>/upgradeBundles-<VxRail cluster id>/
This issue is addressed in VxRail Release 7.0.480 and later. This issue did not exist in the 8.0 VxRail code family. Workaround for earlier 7.0 VxRail code: Copy the relevant firmware files using the vCenter file datastore browser back to the old location: Old Location: /vmfs/volumes/<VSAN datastore>/upgradeBundles/ New Location: /vmfs/volumes/<VSAN datastore>/upgradeBundles-<VxRail cluster id>/ After the file is copied, the VxRail LCM upgrade can be retried or restarted and the file should be found correctly. Note: Should the folder /vmfs/volumes/<VSAN datastore>/upgradeBundles/ not exist, then it can be manually created on the VSAN datastore using the vCenter datastore file browsing page. If any assistance with these steps is required or something is not working as expected, open a Service Request with Dell Technical Support .
Click on a version to see all relevant bugs
Dell Integration
Learn more about where this data comes from
Bug Scrub Advisor
Streamline upgrades with automated vendor bug scrubs
BugZero Enterprise
Wish you caught this bug sooner? Get proactive today.