Update 2025-08-21: CSP-97577 has been pulled.

The CSP-97577 patch instructions (KB 404054) have been updated to reference a new article: KB 406308 – Known Issues after Applying vIDM CSP-97577 Patch. This KB outlines the three issues I highlighted yesterday and provides guidance for affected environments.

After applying the CSP-97577 patch to vIDM, you may encounter::

• Cloud-init Service Failure
  
• Console logs are not shown in the VM console
  
• Certificate Authentication Adapter Load Failure
  Certificate authentication fails if configured before the patch is applied. Check the /opt/vmware/horizon/workspace/logs/connector.log file for this error:
  
  com.vmware.horizon.connector.restapi.identity.exception.mapper.AbstractExceptionMapper - Exception while handling jersey request.java.lang.NoClassDefFoundError: javax/xml/bind/DatatypeConverter at com.vmware.horizon.cas.CASUtil.calculateVersion(CASUtil.java:45)
~[tomcat-support-1.0.jar:3.3.7.0 Build 24863103]

These issues are now documented and addressed in KB 406308.

I can confirm that I successfully updated both a vIDM cluster and the connected ASLCM instance. To make the “Patch Postgres Cluster” action visible for vIDM, I had to clear my browser cache or use a private/incognito window. Additionally, after the patch, I waited until the “Opensearch – unassigned shards” count dropped to around 8,000 before the cluster health transitioned from RED to YELLOW, at which point it reported as healthy: