Deployment of VMware Identity Manager (vIDM) from the vCenter Content Library fails in Aria Suite Lifecycle 8.18.x

Products

• VCF Operations/Automation (formerly VMware Aria Suite)

Issue/Introduction

In VMware Aria Suite Lifecycle 8.18.x specifically Patch 3 and later, deployments utilizing a vCenter Content Library as the binary source may fail during the OVF metadata validation phase. This impact extends to VMware Identity Manager (vIDM).

• Deployment tasks fail during the "Initialize Deployment" or "Validate OVF" stages.

• Failures occur even when the OVA/OVF is present in the Content Library.

• Issues are specifically linked to version/build mismatches between the Lifecycle Manager patch level and the product build.

• Error logs(/var/log/vmware/vrlcm/vrslcm.log) indicate the installation binary cannot be located or verified.
  
  

  "checkName" : "Content Library Item validity check.",
  "checkType" : "ERROR",
  "status" : "FAILED",
  "recommendations" : [ "Make sure the Content Library Item selected is present in the vCenter and contains the ovf package of the corresponding product and version selected. Trigger vCenter data collection to fetch latest vCenter inventory" ],
  "resultDescription" : "Check if the provided content library item Id : ####-#####-##### contains the ovf package of the provided product : vidm and version:                                     
  3.3.7 for component: vidm-primary.",
  "elementType" : "CHECK",

Environment

Aria Suite Lifecycle Manager 8.18.x

Cause

In Aria Suite Lifecycle 8.18 Patch 3 and later, vIDM patch-level parity is strictly enforced. Since manual binary mapping and checksum overrides are now disabled, any version discrepancy between vIDM and the vRSLCM patch level will result in an immediate metadata validation failure within the deployment workflow.

Resolution

Broadcom is aware of this issue, and a permanent fix will be included in an upcoming release. To resolve the issue in the interim, follow the Workaround steps below: 

Workaround:

Manually Update Checksum Metadata

   Note: Ensure a snapshot without memory is captured for the Aria Suite Lifecycle appliance to serve as a rollback point if needed.

1. Log in to the Aria Suite Lifecycle appliance via SSH as root.

2. Navigate to the VIDM checksum repository: cd /data/vm-config/vmrepo/checksumRepo/vi/vidm337




3. Open the file "vidm337" in the editor. 
4. Locate the entry containing "binaryType": "install".

5. Find the "binaryName" field and update the build number to match the exact string found in your vCenter Content Library. (Logon to vCenter > Navigation Menu > Content Libraries > Select the target Library and extract the Full Build String for the vIDM 3.3.7 OVA/OVF.This value is required to synchronize the Aria Suite Lifecycle checksum repository.)

   
   
   
   
   
   

6. Save and exit the file (:wq!).

7. Return to the vRSLCM UI and Resume the deployment.