🔄 Update 2025-08-05: It turns out both Broadcom support and I may have been a bit early in expecting a patch release. As of now, there’s no confirmed ETA for the updated vIDM patch. However, Broadcom has confirmed that a knowledge base (KB) article is in the works to address known issues with patch CSP-97577.

These reported issues include:

• After Patch is applied and the vIDM machine is rebooted, the cloud-int service Failed log message on vCenter Console
• After Patch, Console logs are not shown in the VM console
• If the Certificate Auth Adapter is configured in vIDM and Patch is Applied, the cert auth breaks.
  ⚠️ This only applies if Cert Auth was already configured in vIDM before the patch.

Additionally, the missing Day-2 Postgres patching option in ASLCM appears to be a browser caching issue, not a platform-level bug.

📝 Original post below.

⚠️ Heads-up for anyone about to patch ASLCM with VMware Identity Manager installed and managed by VMware Aria Suite Lifecycle

Following up on my recent post about ASLCM failing to mount /boot after patching (which required editing /etc/fstab), I proceeded to patch another vIDM instance (which was a cluster of 3 nodes), per the ASLCM release notes. After that, I patched the connected ASLCM instance (with the fstab fix in place), and ASLCM came back online as expected.

However, the Day-2 option for vIDM Postgres patching in ASLCM was nowhere to be found. I opened a support case to confirm I followed the correct procedure, and I had. But support informed me that a new patch for vIDM is expected to be released later today due to issues in the previous one.

Recommendation: If you haven’t patched vIDM yet, it’s best to hold off until the updated patch is available. It seems the previous patch bundle had an issue.

🕓 I’ll update this post with a link to the patch, release notes, or KB article once it becomes available. The release will likely drop during U.S. business hours today.