Patching ESXi host with a custom image failed with error: "'SET DESIRED STATE' failed from SDDC Manager"

Products

• VMware SDDC Manager

Issue/Introduction

Upgrading ESXi hosts using SDDC manager is getting failed at 'SET DESIRED STATE' stage.

lcm.log
yyyy-mm-ddT11:20:13.126+0000 ERROR [vcf_lcm,0000000000000000,0000] [c.v.e.s.l.orch.PrimitiveServiceImpl,Upgrade-1] primitive post upgrade returned exception
com.vmware.evo.sddc.lcm.model.error.LcmException: Setting desired state failed
        at com.vmware.evo.sddc.lcm.primitive.impl.cluster.VlcmUpdateStageRunnerImpl.doSetDesiredState(VlcmUpdateStageRunnerImpl.java:1083)
        at com.vmware.evo.sddc.lcm.primitive.impl.cluster.VlcmUpdateStageRunner.doStage(VlcmUpdateStageRunner.java:171)
        at com.vmware.evo.sddc.lcm.primitive.impl.cluster.VlcmPrimitiveImpl.runUpgrade(VlcmPrimitiveImpl.java:516)
        at com.vmware.evo.sddc.lcm.primitive.impl.cluster.VlcmPrimitiveImpl.startOrResumeUpgrade(VlcmPrimitiveImpl.java:262)
        at com.vmware.evo.sddc.lcm.primitive.impl.cluster.VlcmPrimitiveImpl.postUpgrade(VlcmPrimitiveImpl.java:205)
        at com.vmware.evo.sddc.lcm.orch.PrimitiveServiceImpl.postUpgradeAsync(PrimitiveServiceImpl.java:323)
        at com.vmware.evo.sddc.lcm.orch.PrimitiveServiceImpl.lambda$postUpgrade$0(PrimitiveServiceImpl.java:165)
        at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136)
        at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)
        at java.base/java.lang.Thread.run(Thread.java:840)
yyyy-mm-ddT11:20:22.548+0000 INFO  [vcf_lcm,67fa4c767fe7278a101ae68b65770902,9ae4] [c.v.evo.sddc.lcm.orch.Orchestrator,vac-scheduler-1] Started orchestrating upgrade e219aef0-dd58-4351-a59e-979aaac95871
yyyy-mm-ddT11:20:22.552+0000 INFO  [vcf_lcm,67fa4c767fe7278a101ae68b65770902,9ae4] [c.v.evo.sddc.lcm.orch.Orchestrator,vac-scheduler-1] Upgrade e219aef0-dd58-4351-a59e-979aaac95871 reached final state COMPLETED_WITH_FAILURE

Environment

VMware Cloud Foundation 4.x
VMware Cloud Foundation 5.x

Cause

This can happen when the latest version(s) of the vendor add-on haven't yet been added to the VMware download sources.

Resolution

Apply the resolution provided in the KB326246
Newer versions of a vendor add-on might be missing when configuring a Lifecycle Manager cluster image in vCenter Server 7.0/8.0
https://knowledge.broadcom.com/external/article/326246/newer-versions-of-a-vendor-addon-might-b.html