Intermittent authentication issues and failure to gather logs from vIDM three node cluster

Products

• VCF Operations/Automation (formerly VMware Aria Suite)

Issue/Introduction

- Authentication failures using vIDM

- Postgres clustering status shows as critical for globalenvironment object in Aria Suite Lifecycle

- Manual remediation using this kb: Troubleshooting VMware Identity Manager postgres cluster deployed through Aria Suite Lifecycle (vRSLCM) works but the postgres critical error issue recurs

- When trying to power on the cluster from LCM you see the below error: 

Error Code: LCMVIDM73101
Couldn't get vIDM health status after max retries. Refer to VMware Aria Suite Lifecycle log for additional details.
Couldn't get vIDM health status after maximum retries on the host(s) - <vidm node hostnames>. The health API might fail, even when the horizon service is down. Ensure if the health is ok on the vIDM node(s) and retry.

- When trying to gather the vIDM logs from LCM you see the below error: 

Error Code: LCMGENSBVIDM71302 - "Could not resolve view with name 'ajaxResponse' in servlet with name"

but this is not resolved by applying this kb: Unable to collect VIDM logs from LCM or directly from 8443 page - "Could not resolve view with name 'ajaxResponse' in servlet with name"

Environment

vIDM three node cluster 3.3.7

Cause

One or more of the cluster nodes has the incorrect root password configured in Aria Suite Lifecycle. This impacts LCMs ability to manage the nodes. In particular it will prevent the management of postgres clustering as well as the ability to gather log bundles from the nodes. 

Resolution

Update the password locker to match the correct root password for all vIDM nodes. 

You can view the value of the locker object stored in LCM by following this kb: Viewing passwords stored in VMware Aria Suite Lifecycle (vRealize Suite Lifecycle Manager) Locker

You can then create a new locker object for the new password and perform an inventory sync to update LCM yo use this password.