vIDM cluster UI becomes unreachable after enabling Cluster Auto-Recovery via Aria Suite Lifecycle

Products

• VCF Operations/Automation (formerly VMware Aria Suite)

Issue/Introduction

• vIDM cluster UI is unreachable after enabling Cluster Auto-Recovery via Lifecycle Manager.
• The vIDM cluster status appears healthy when checking Postgres and Watchdog status via CLI.
• A delegateIP is assigned to the primary node, but communication fails. 

Environment

vIDM 3.3.7

Cause

This issue can occur because the /etc/hosts file on one or more vIDM nodes contains tab characters instead of standard whitespace (spaces) between the IP addresses and hostnames.

The Auto-Recovery automation and horizon services may fail to parse network configurations correctly when tabs are present. 

Resolution

1. Take Snapshots: Before making changes, take a snapshot of all vIDM nodes in the cluster.
2. Edit the Hosts File: SSH into each vIDM node and open /etc/hosts for editing:

   vi /etc/hosts

3. Correct Formatting: Replace any tab characters with standard spaces.
4. Restart Services: Run the following command on all nodes to apply the changes

   service horizon-workspace restart