Adding a Work Load Domain (WLD) in Vxrail failed with Error: Error in validating VxRail payload. Failed to fetch the images from LCM Service with error.
search cancel

Adding a Work Load Domain (WLD) in Vxrail failed with Error: Error in validating VxRail payload. Failed to fetch the images from LCM Service with error.

book

Article ID: 406416

calendar_today

Updated On:

Products

VMware Cloud Foundation

Issue/Introduction

  • Online depot is actively in use.
  • Both Dell depot & VMware depot are connected fine.
  • After providing all the details under VxRail VI Configuration, the process fails immediately at validation stage with following error:

LCM unable to detect the current ESXi versions from SDDC, since /opt/vmware/vcf/lcm/lcm-app/conf/application-prod.properties is not updated properly.

/var/log/vmware/vcf/lcm/lcm.log:

####-##-##T##:##:##.###+#### ERROR [vcf_1cm, ###################, ####] [c.v.e. s. 1.s. i. ImageManagementServiceImpl, vac-scheduler-1] Exception while getting version compliance matrix for VI domain - {)
com.vmware.evo.sddc.lcm.model.error.LcmException: The Install version set mentioned in the property file has a missing entry for either of VCENTER, ESX, NSX

/var/log/vmware/vcf/domainmanager/domainmanager.log

####-##-##T##:##:##.###+####  DEBUG [vcf_dm,401b5cce274d4065,b48d] [c.v.e.s.e.h.LocalizableRuntimeExceptionHandler,http-nio-127.0.0.1-7200-exec-4]  Handler Error Response: {"errorCode":"FAILED_TO_FETCH_IMAGES","arguments":[""],"mess
age":"Failed to fetch the images from LCM Service with error: .","remediationMessage":"Download the necessary images and retry the workflow.","causes":[{"type":"com.vmware.cloud.foundation.rest.lcm.runtime.ApiException","message":"
"}],"referenceToken":"FB5IQB"}

Environment

VCF on vXrail 5.x

VMware SDDC Manager

Cause

While providing data under VxRail VI Configuration wizard, under General info - Lifecycle Management, the option "Manage clusters in this workload domain using vLCM images" is checked.

  • When this option is chosen, the process will look for the current versions of Vcenter, ESXi & NSX in the current environment, by accessing the application-prod.properties file under /opt/vmware/vcf/lcm/lcm-app/conf/.
  • The issue occurs if application-prod.properties file is missing a line or it is hashed out.

Example on the faulty entries as follows.

Example 1: (#)

vcenter.install.version=8.0.3.00400-24322831
nsxt.install.version=4.2.1.3.0-24533884
#esx.install.version=8.0.3-24585383

Example 2: (Missing values)

vcenter.install.version=8.0.3.00400-24322831
nsxt.install.version=4.2.1.3.0-24533884

On the above examples, esx.install.version value cannot be detected by LCM as it is hashed out/missing.

Resolution

  • Take a snapshot of SDDC appliance.
  • Open SSH session of SDDC & login as root.
  • Edit the application-prod.properties file using vi editor. 
cd /opt/vmware/vcf/lcm/lcm-app/conf/

vi application-prod.properties
  • Go to the last line of the file that contains all the install values of Vcenter, NSX & ESX.
  • Press Insert key.
  • Remove the # & save the file or add the missing value & save the file.

The result should look like,

vcenter.install.version=8.0.3.00400-24322831
nsxt.install.version=4.2.1.3.0-24533884
esx.install.version=8.0.3-24585383
  • Press ESC key & type :wq! to save the file.

Note: The build numbers given are examples. The actual build number may differ based on the environment.

  • Restart the LCM service.
systemctl restart lcm
  • Retry adding Work Load Domain.