HA failed at VC upgrade
Article ID: 313311
Updated On:
Products
Issue/Introduction
This article explains about the HA issues observed after the VC Upgrade.
Symptoms:
After VC upgrade, VUM/vLCM service is restarted. At this time, VC sets new HA using vLCM, This operation may fail with:
2023-03-17T14:23:01.962Z info vmware-vum-server[08406] [Originator@6876 sub=com.vmware.vcIntegrity.lifecycle.SetSolutionTask] [Task, 486] Task:com.vmware.vcIntegrity.lifecycle.SetSolutionTask ID:5288e1cf-9575-3b7e-2b0f-13e9de1d2a59. Task Finalization completed.^M
2023-03-17T14:23:01.962Z error vmware-vum-server[08406] [Originator@6876 sub=com.vmware.vcIntegrity.lifecycle.SetSolutionTask] [Task, 486] Task:com.vmware.vcIntegrity.lifecycle.SetSolutionTask ID:5288e1cf-9575-3b7e-2b0f-13e9de1d2a59. Task Failed. Error: Error:^M
--> com.vmware.vapi.std.errors.invalid_argument^M
--> Messages:^M
--> com.vmware.vcIntegrity.lifecycle.softwarespec.InvalidImage<Image is not valid.>^M
--> ^M
The issue is intermittent.
Environment
Cause
At VUM/vLCM service restart, it validates/loads VMware online depots and other online depots customers added; also it loads HA/WCP depots from vCenter to vLCM. Due to the size of the online depots, validating/loading them needs time. This may block HA depot load which needs the write lock of depot cache by the depot validation operation which holds the read lock or the load operation which holds thee write lock.
On the other hand, if HA upgrade operation comes early before the depot loads finish. This operation validates the desired image with the new version of HA component.
However, as the depot is not ready yet, the new version of HA component is not found. Thus, software validation fails with error mentioned above.
Resolution
This is the behavior for multiple releases. Due to the accumulation of base images and add-ons, depot validation/load becomes heavier so the issue becomes more often.
Workaround:
Customer can disable/enable HA to fix the issue.
Feedback
