Setting up vLCM image on the cluster fails with the error "Failed to verify whether cluster contains payload from unsupported solution(s)."
search cancel

Setting up vLCM image on the cluster fails with the error "Failed to verify whether cluster contains payload from unsupported solution(s)."

book

Article ID: 312995

calendar_today

Updated On:

Products

VMware vSphere ESXi

Issue/Introduction

Symptoms:

When we try to setup image on the cluster, it gets stuck at 24% and fails with the error "Failed to verify whether cluster contains payload from unsupported solution(s)."

 

In /var/log/vmware/vmware-updatemgr/vum-server/vum-server.log we might see the below events

2023-00-00T00:00:00.000Z error vmware-vum-server[11022] [Originator@6876 sub=ImageManager::EnablementManager] [EnablementManager 1132] Failed to get installed components result from 'ESXi_FQDN' host. Error: No diagnostic information available.
 

2023-00-00T00:00:00.000Z error vmware-vum-server[11022] [Originator@6876 sub=com.vmware.vcIntegrity.lifecycle.CheckFeatureApplicabilityTask] [Task, 457] Task:com.vmware.vcIntegrity.lifecycle.CheckFeatureApplicabilityTask ID:526659f9-b49f-9a05-cfbf-65a2c4f3f599. Task Failed. Error: Error:

-->  com.vmware.vapi.std.errors.error

--> Messages:

-->  com.vmware.vcIntegrity.lifecycle.enablement.EligibilityCheck.UnsupportedSolution.Failure<Failed to verify whether cluster contains payload from unsupported solution(s).>

-->

2023-00-00T00:00:00.000Z warning vmware-vum-server[12116] [Originator@6876 sub=TaskStatsCollector] [taskStatsCollector 190] Task type or creation time not present

2023-00-00T00:00:00.000Z info vmware-vum-server[11022] [Originator@6876 sub=PM.AsyncTask.CheckFeatureApplicabilityTask{97}] [vciTaskBase 1372] SerializeToVimFault fault:

--> (vmodl.fault.SystemError) {

-->  faultCause = (vmodl.MethodFault) null,

-->  faultMessage = (vmodl.LocalizableMessage) [

-->    (vmodl.LocalizableMessage) {

-->     key = "com.vmware.vcIntegrity.lifecycle.enablement.EligibilityCheck.UnsupportedSolution.Failure",

-->     arg = <unset>,

-->     message = <unset>

-->    }

-->  ],

-->  reason = "vLCM Task failed, see Error Stack for details."

 -->  msg = "{

 -->   "data": null,

 -->   "error_type": "ERROR",

 -->   "messages": [

 -->     {

 -->       "args": [],

 -->       "default_message": "Failed to verify whether cluster contains payload from unsupported solution(s).",

 -->       "id": "com.vmware.vcIntegrity.lifecycle.enablement.EligibilityCheck.UnsupportedSolution.Failure"

 -->     }

 

 

 

 

Environment

VMware vSphere 8.x
VMware vSphere 7.x

Cause

This issue can occur if the there are two management networks enabled on any host in the cluster.

 

Interface NetstackInstance  Tags

  --------- ----------------  ----

  vmk0    defaultTcpipStack Management

  vmk1    defaultTcpipStack VSAN, Management

  vmk2    defaultTcpipStack blank in esxcfg-info_-a.txt

  vmk3    defaultTcpipStack VMotion, vSphereProvisioning

 

 

Resolution

Please ensure to have just one Management network on the host. If there are multiple Management network flag enabled, please edit the respective VMkernel adapter configuration and uncheck the Management flag and save the configuration.

Impact

Cannot setup image on the cluster.

Additional Information

This issue can also be cause if each ESXI host in the cluster share the same scratch location. Each host needs a unique logdir for the scratch location to be configured to.

Settingsd Log indicate that there is a shared scratch location between multiple ESXi hosts, so only one of the hosts is able to access the file: /var/vmware/lifecycle/task-status.json.db and is inaccessible by other hosts and so the settingsd service crashes and that causes VLCM setup failure

In /var/run/log/settingsd we might see the below events

2024-04-30T18:11:27.832Z Er(11) settingsd[25194394]: [/var/vmware/lifecycle/task-status.json.db] unable to open DB: unable to open database file
2024-05-01T19:23:14.260Z In(30) settingsd[2099349]: settingsd started
2024-05-01T19:23:14.351Z In(14) settingsd[2099348]: Log for unknown version=unknown build=unknown option=unknown
2024-05-01T19:23:14.351Z In(14) settingsd[2099348]: Using VMware ESXi syslog APIs
2024-05-01T19:23:14.351Z In(14) settingsd[2099348]: PREF early PreferenceGet(log.syslogID), using default
2024-05-01T19:23:14.351Z In(14) settingsd[2099348]: PREF early PreferenceGet(settingsd.log.syslogID), using default
2024-05-01T19:23:14.351Z In(14) settingsd[2099348]: PREF early PreferenceGet(log.syslogLevel), using default
2024-05-01T19:23:14.351Z In(14) settingsd[2099348]: PREF early PreferenceGet(settingsd.log.syslogLevel), using default
2024-05-01T19:23:14.351Z In(14) settingsd[2099348]: PREF early PreferenceGet(log.stderrLevel), using default
2024-05-01T19:23:14.351Z In(14) settingsd[2099348]: PREF early PreferenceGet(settingsd.log.stderrLevel), using default
2024-05-01T19:23:14.351Z In(14) settingsd[2099348]: PREF early PreferenceGet(log.syslogFacility), using default
2024-05-01T19:23:14.351Z In(14) settingsd[2099348]: PREF early PreferenceGet(settingsd.log.syslogFacility), using default
2024-05-01T19:23:14.351Z In(14) settingsd[2099348]: PREF early PreferenceGet(log.syslogRetries), using default
2024-05-01T19:23:14.351Z In(14) settingsd[2099348]: PREF early PreferenceGet(settingsd.log.syslogRetries), using default
2024-05-01T19:23:14.351Z In(14) settingsd[2099348]: PREF early PreferenceGet(log.syslogDelay), using default
2024-05-01T19:23:14.351Z In(14) settingsd[2099348]: PREF early PreferenceGet(settingsd.log.syslogDelay), using default
2024-05-01T19:23:22.368Z Er(11) settingsd[2099348]: [/var/vmware/lifecycle/task-status.json.db] unable to open DB: unable to open database file

Creating a persistent scratch location for ESXi 8.x/7.x/6.x

 

Powered by Wolken Software