Transition to vSphere Lifecycle Manager (vLCM) Images using SDDC Manager fails with error "Cluster is not eligible for enabling vSphere Lifecycle Manager Images. Failed with error: Data value is required"

Products

• VMware SDDC Manager

Issue/Introduction

• Cluster been converted from Baselines to vSphere Lifecycle Manager Images(vLCM) in SDDC managed environment following KB385617.
  
  
• Conversion failing in cluster eligibility check with error:
  

  Cluster <cluster_name> is not eligible for enabling vSphere Lifecycle Manager Images. Failed with error: Data value is required

• vCenter lcm logs reporting the following error:
  
  /var/log/vmware/vmware-updatemgr/vum-server/vmware-vum-server.log
yyyy-mm-ddThh:mm:ss.zzzZ info vmware-vum-server[3587085] [Originator@6876 sub=com.vmware.vcIntegrity.lifecycle.CheckFeatureApplicabilityTask opID=<op_id>] [Task, 524] Task:com.vmware.vcIntegrity.lifecycle.CheckFeatureApplicabilityTask ID:<task_id>. Task Created
yyyy-mm-ddThh:mm:ss.zzzZ info vmware-vum-server[1969120] [Originator@6876 sub=com.vmware.vcIntegrity.lifecycle.CheckFeatureApplicabilityTask] [Task, 524] Task:com.vmware.vcIntegrity.lifecycle.CheckFeatureApplicabilityTask ID:<task_id>. Starting task: com.vmware.vcIntegrity.lifecycle.CheckFeatureApplicabilityTask, cluster: <domain_id>(<domain_name>), user: <sso_administration_account>
yyyy-mm-ddThh:mm:ss.zzzZ info vmware-vum-server[1969120] [Originator@6876 sub=ImageManager::EnablementManager] [EnablementManager 1437] Retrieving installed components for '<host_fqdn>' host.
yyyy-mm-ddThh:mm:ss.zzzZ info vmware-vum-server[1969120] [Originator@6876 sub=ImageManager::EnablementManager] [EnablementManager 1443] Retrieving orphan vibs for '<host_fqdn>' host.
yyyy-mm-ddThh:mm:ss.zzzZ error vmware-vum-server[1969120] [Originator@6876 sub=ImageManager::EnablementManager] [EnablementManager 1579] Retrieving installed components for '<host_fqdn>' host timed out
yyyy-mm-ddThh:mm:ss.zzzZ error vmware-vum-server[1969120] [Originator@6876 sub=ImageManager::EnablementManager] [EnablementManager 1894] Failed to retrieve payload information for '<domain_id>' cluster.
yyyy-mm-ddThh:mm:ss.zzzZ error vmware-vum-server[1969120] [Originator@6876 sub=com.vmware.vcIntegrity.lifecycle.CheckFeatureApplicabilityTask] [Task, 524] Task:com.vmware.vcIntegrity.lifecycle.CheckFeatureApplicabilityTask ID:<task_id>. SOFTWARE check failed for '<domain_id>(<domain_name>)' cluster.
yyyy-mm-ddThh:mm:ss.zzzZ error vmware-vum-server[1969120] [Originator@6876 sub=com.vmware.vcIntegrity.lifecycle.CheckFeatureApplicabilityTask] [Task, 524] Task:com.vmware.vcIntegrity.lifecycle.CheckFeatureApplicabilityTask ID:<task_id>. Task Failed. Error: 
Error:
-->    com.vmware.vapi.std.errors.error
--> Messages:
-->    com.vmware.vcIntegrity.lifecycle.enablement.EligibilityCheck.UnsupportedSolution.Failure<Cluster contains payload from unsupported solution(s).>
-->
yyyy-mm-ddThh:mm:ss.zzzZ warning vmware-vum-server[58615] [Originator@6876 sub=TaskStatsCollector] [taskStatsCollector 190] Task type or creation time not present
yyyy-mm-ddThh:mm:ss.zzzZ info vmware-vum-server[1969120] [Originator@6876 sub=PM.AsyncTask.CheckFeatureApplicabilityTask{4422}] [vciTaskBase 1496] SerializeToVimFault fault:
..
--> Converted fault:
--> (vim.fault.ExtendedFault) {
-->    faultCause = (vmodl.MethodFault) null,
-->    faultMessage = (vmodl.LocalizableMessage) [
-->       (vmodl.LocalizableMessage) {
-->          key = "com.vmware.vcIntegrity.lifecycle.enablement.EligibilityCheck.UnsupportedSolution.Failure",
-->          arg = <unset>,
-->          message = <unset>
-->       }
-->    ],
-->    faultTypeId = "SystemError",
-->    data = (vim.KeyValue) [
-->       (vim.KeyValue) {
-->          key = "faultCause",
-->          value = ""
-->       },
-->       (vim.KeyValue) {
-->          key = "reason",
-->          value = "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

VMware SDDC Manager 9.x
VMware SDDC Manager 5.x

Cause

 The eligibility check will fail if there are issues with the hosts in the cluster communication with the vCenter Server.

Resolution

The investigation should proceed to determine any ESXi Host - vCenter communication issues, which can be due to various reasons including:

• ESXi host being in a "not responding" or "disconnected" state
• An ESXi host misconfiguration or underlying issue
• A network misconfiguration
• Required TCP/UDP ports blocked by a firewall/proxy
• NTP/DNS issue

Additional Information

Transition to vSphere Lifecycle Manager (vLCM) Images using SDDC Manager

Feature cannot be enabled on this cluster when trying to convert a cluster to vLCM Single Image Managed

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

"Payload of unsupported Workload Management solution has been identified on the following host(s)" while configuring the single image cluster using vLCM.

Converting a cluster to image-based fails with "Cluster contains payload from unsupported solution(s)." when the host has an invalid scratch configuration

Troubleshooting an ESXi host in a "not responding"/"disconnected" state