'Error Code: LCMVROPCONFIG20066 VMware Aria Operations Config Error: Unknown Host Exception' seen during inventory sync in Aria Suite Lifecycle

Products

• VMware Aria Suite

Issue/Introduction

Symptoms:

• Aria Operations inventory sync fails in Aria Suite Lifecycle with:
  
  Error Code: LCMVROPCONFIG20066 VMware Aria Operations Config Error: Unknown Host Exception. Retry with correct hostname. If hostname is correct, ensure either VMware Aria Operations DNS server is present in VMware Aria Suite Lifecycle or VMware Aria Operations entries are present in the DNS server of VMware Aria Suite Lifecycle. VMware Aria Operations master node address provided is not resolvable <null/hostname>

• The /var/log/vrlcm/vmware_vrlcm.log contains below details:
  
  INFO  [pool-3-thread-31] c.v.v.l.p.a.s.Task -  -- Injecting task failure event. Error Code : 'LCMVROPCONFIG20066', Retry : 'true', Causing Properties : '{ CAUSE :: vropsMasterNodeIP === skipTask ===  }'com.vmware.vrealize.lcm.util.certificate.exceptions.EngineException: VMware Aria Operations master node address provided is not resolvable null at com.vmware.vrealize.lcm.plugin.core.vrops.tasks.StartDiscoveryTask.checkVrops(StartDiscoveryTask.java:103) [vmlcm-vropsplugin-core-8.16.0-SNAPSHOT.jar!/:?]

Environment

VMware vRealize Suite Lifecycle Manager 8.x

VMware Aria Suite Lifecycle 8.x

Cause

The error can occur due to DNS issues, problems with the Aria Operations hostname or null value towards the VMware Aria Operations master node within Aria Lifecycle Manager.

Resolution

To resolve the issue perform the following steps:

 

1.  Validate that the Aria Suite Lifecycle appliance and Aria operations appliance can resolves each others hostnames. SSH to each appliance and use the nslookup command to validate name resolution:

   nslookup <Aria Operations/Aria Suite Lifecycle FQDN>

2.  Validate that Aria Operations has the correct hostnames set, to change the Aria Operations hostname you can follow KB 2108689

3.  To update Aria Suite Lifecycle's reference to the Aria Operations hostname trigger again the inventory sync , once it fails select the Retry option and manually enter the correct FQDN & credentials of the Aria Operations appliance.

4.  If the above steps fail to resolve the issue you can remove and re-import the Aria Operations from Aria Suite Lifecycle.

     To remove the Aria Operations environment from Aria Suite Lifecycle select the Delete Environment action, followed by the Delete Environment from VMware Aria Suite Lifecycle option

     * Do Not select the Delete associated VMs from vCenter option. As this will permanently delete the Aria Operation appliances from vCenter.

     To import again the Aria Operation environment follow the steps in the Aria Suite Lifecycle Import a VMware Aria Operations environment

5.  Perform a manual failover (Graceful shutdown and then Power ON Master Node) for HA cluster from Aria Operations admin UI. (https://<AriaOperations-FQDN/IP>/admin)

     Make sure from the Aria Operations Admin UI that Primary and Primary Replica cluster roles are assigned properly.

     Re-trigger the inventory sync for Aria Operations environment in Aria LifeCycle Manager.