vLCM image setup fails with "Cluster contains payload from unsupported solution(s)" due to ESXi DNS resolution failure
search cancel

vLCM image setup fails with "Cluster contains payload from unsupported solution(s)" due to ESXi DNS resolution failure

book

Article ID: 455304

calendar_today

Updated On:

Products

VMware vCenter Server VMware vSphere ESXi

Issue/Introduction

  • When accessing "Manual Image Settings" in vLCM, a general system error occurs: "The cluster contains payloads of unsupported solutions."
  • vmware-vum-server-###.log shows as following:
YYYY-MM-DDTHH:MM:SS.###+09:00 warning vmware-vum-server[11102] [Originator@6876 sub=TaskStatsCollector] [taskStatsCollector 190] Task type or creation time not present
YYYY-MM-DDTHH:MM:SS.###+09:00 warning vmware-vum-server[18316] [Originator@6876 sub=IO.Connection] Failed to resolve address; <resolver p:0x0000############, '<host name>:443', next:(null)>, e: 1(Host not found (authoritative)), async: true, duration: 0msec
YYYY-MM-DDTHH:MM:SS.###+09:00 info vmware-vum-server[321802] [Originator@6876 sub=PM.AsyncTask.CheckFeatureApplicabilityTask{54}] [vciTaskBase 1496] 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": "Cluster contains payload from unsupported solution(s).",
-->             "id": "com.vmware.vcIntegrity.lifecycle.enablement.EligibilityCheck.UnsupportedSolution.Failure"
-->         }
-->     ]
--> }"
--> }

Environment

vCenter Server 8.x

vCenter Server 7.x

vSphere ESXi 8.x

vSphere ESXi 7.x

Cause

vCenter Server failed to resolve the ESXi host FQDN, which blocked the vLCM eligibility check.

Resolution

To resolve this issue, ensure that bidirectional name resolution (Forward and Reverse DNS) is correctly configured between the vCenter Server and all ESXi hosts in the cluster.

  1. Verify vCenter Server Resolution: Ensure the vCenter Server can resolve the Fully Qualified Domain Names (FQDNs) of all ESXi hosts in the cluster.
    1. Log in to the vCenter Server Appliance (VCSA) via SSH.
    2. Run nslookup <ESXi-Host-FQDN> to confirm resolution.
  2. Verify ESXi Host Resolution: Ensure each ESXi host can resolve the vCenter Server FQDN.
    1. Log in to the ESXi host via SSH.
    2. Verify DNS configuration using esxcli network ip dns server list and check /etc/resolv.conf.
    3. Run nslookup <vCenterServer-FQDN> to confirm resolution
  3. Retry vLCM Operation: Navigate back to the cluster Updates tab and attempt to access the Image settings again.