The Identity Broken Endpoint Instance in VCF Operations 9.0.2 is stuck in "no Data Receiving" status

Products

• VCF Operations

Issue/Introduction

The management adapter log is throwing an "UnknownHostException" and shows the error: Cannot contact endpoint <IDB FQDN>

From the latest ManagementAdapter.log we see repeated errors:

ERROR ManagementAdapter 319731 [ops@4413 threadId=”561” threadName=”Collector worker thread 11” instanceId=”397”] 
[(397 com.vmware.adapter.management.components.iam.resource.VidbResourceManager.getVidbReadiness] – 
exception while getting vidb readiness metric from endpoint <IDB FQDN>
Com.vmware.adapter.management.components.iam.exception.EndpointUnreachable: Cannot contact endpoint <IDB FQDN>
Caused by: java.net.UnknownHostException: <IDB FQDN>: Temporary failure in name resolution
Exception while calling get all dlap configuration for vidb ldap sync alert
Cannot query SCIM sync client token expiration data on endpoint <IDB FQDN> because it is unreachable

Environment

VCF Operations 9.0x

Cause

The specific VCF Operations collector node attempting to pull the data cannot locally resolve the Fully Qualified Domain Name (FQDN) of the Identity Broker to an IP address.

Resolution

As a temporary work around:

modify the /etc/hosts file on the VCF Operations collector node to include the target's routing details:
<IP_Address_of_IDB> <IDB_FQDN>

Additional Information

Because this fix relies on a hardcoded IP address in the /etc/hosts file, this entry will need to be manually updated if the internal IP address of the Identity Broker Endpoint is ever changed.

If the Identity Broker is rebuilt, migrated it, or changes its internal IP address in the future, collection will fail again until that /etc/hosts file is updated to reflect the new IP.