Deployment of VCF Operations for Logs 9.0.2 fails with Error Code LCMVSPHERECONFIG1000073 When Using Automation Tools or API

Products

• VCF Operations/Automation (formerly VMware Aria Suite)

Issue/Introduction

• When deploying VMware Cloud Foundation Operations for Logs 9.0.2 using automation tools or API, the deployment may fail with the following error:
   
  

  Error Code: LCMVSPHERECONFIG1000073
  Error while using the ova file for deployment. Check the correctness of the file. Ensure that ova is mapped in Settings-Binary Mapping.
  File : http://localhost:8080/repo/productBinariesRepo/vrli/9.0.2.0.25137850/install/vrli.ova not found.

   

• Reviewing the /var/log/vrlcm/vmware_vrslcm.log on the Fleet Management appliance reveals below error
  
  

  "products" : [ {
  "vmid" : "#######-####-####-####-#########",
  "tenant" : "default",
  "version" : "9.0.2.0.25137850",
  "id" : "vrli",
  "productUuid" : "#######-####-####-####-#########",
  "clusterVIP" : {
  "clusterVips" : [ {
  "type" : "vrli-cluster-1",
  "properties" :
  
  { "hostName" : "<VCF_Logs-FQDN>", "ip" : "<VCF_Logs-IP>" }
  } ]
  
  INFO vrlcm[####] [http-nio-####-exec-9] [c.v.v.l.c.c.FileContentDatabase] – Decoded query url ::/productBinariesRepo/vrli/9.0.2.0.25137850/install/vrli.ova
  ERROR vrlcm[####][http-nio-####-exec-9] [c.v.v.l.c.c.FileContentDatabase] – content not present
  ERROR vrlcm[####] [pool-3-thread-95] [c.v.v.l.p.c.v.t.ValidateDeployInputsTask] – Invalid File error.
  INFO vrlcm[####] [pool-3-thread-95] [c.v.v.l.p.a.s.Task] – Injecting task failure event. Error Code : 'LCMVSPHERECONFIG1000073', Retry : 'true', Causing Properties : '
  
  { CAUSE :: installerLocation === }
  '
  com.vmware.vrealize.lcm.drivers.vsphere65.domain.InvalidFileException: File : http://localhost:8080/repo/productBinariesRepo/vrli/9.0.2.0.25137850/install/vrli.ova not found.
  at com.vmware.vrealize.lcm.plugin.core.vsphere.tasks.ValidateDeployInputsTask.execute(ValidateDeployInputsTask.java:399) [vmlcm-vsphereplugin-core-9.0.2.0-SNAPSHOT.jar!/:?]

  
  
  

• Running the following database query confirms that the expected mapped URL exists in the binary repository on the Fleet Management appliance.

  Note : Use the following command to connect to the database: psql -d vrlcm -U postgres -h localhost

  vrlcm=# select content, url from vm_cr_content as vcc, vm_cr_contentdownloadurl as vcd where vcc.vmid=vcd.content and reponame='productBinariesRepo';
  content | url
  -------------------------------------+----------------------------------------------------------
  #########-####-####-####-########### | /productBinariesRepo/vrops/9.0.2.0/install/vrops.ova
  #########-####-####-####-########### | /productBinariesRepo/vrops/9.0.2.0/install/cloudproxy.ova
  #########-####-####-####-########### | /productBinariesRepo/vrli/9.0.2.0/install/vrli.ova
  

Environment

VCF Operations for Logs 9.0.2

Cause

• This issue occurs when the deployment automation script or API payload passes the full product version string, including the build number (e.g., 9.0.2.0.25137850). The lifecycle management engine uses this input to construct the file path for retrieving the binary. Because the directory structure in the repository maps to the 4-digit release version rather than the specific build string, the constructed path is invalid, resulting in a file not found error.

Resolution

• Modify the deployment request API payload to reference the correct repository path.
• Ensure the path uses the 4-digit release version instead of the full build string.
• Update the repository path to the following:
      /productBinariesRepo/vrli/9.0.2.0/install/vrli.ova
• After updating the payload, retry the deployment.