Aria Automation Cloud Accounts intermittently enter a Warning state, resulting in data collection failures.
The following error can be seen upon accessing the Cloud Account: Data Collection failed
java.util.concurrent.CompletionException: com.vmware.photon.controller.model.adapters.vsphere.VsphereAdapterException: The connection with vPI endpoint can not be established. Cause: java.net.UnknownHostException: <vCenter name>: Temporary failure in name resolution
The nslookup command intermittently failed or timed out with the following error:
cat /etc/resolv.conf
nameserver ##.##.##.101
nameserver ##.##.##.102
nslookup vcenter.example.com ##.##.##.101
nslookup vcenter.example.com ##.##.##.102
Intermittent failures in DNS resolution, specifically caused by a problematic DNS server, result in the Aria Automation nodes being unable to reliably resolve the Cloud Accounts' hostnames.
This leads to the "java.net.UnknownHostException: <vCenter name>: Temporary failure in name resolution"
error.
Identify and remove the problematic DNS server IP address from the /etc/resolv.conf
file on all Aria Automation nodes.
Use the following document to update/add DNS in Aria Automation: Update the DNS assignment for VMware Aria Automation
Engage the DNS/internal network teams to investigate and resolve the underlying DNS or network stability issues to prevent future occurrences.
Intermittent DNS issues can result in cloud accounts entering a warning state even if services like vCenter or NSX-T are otherwise healthy.
Consistent DNS resolution is critical for proper functioning of Aria Automation integrations.
Administrators are advised to work with internal DNS/networking teams to ensure stability and remove any failing or unresponsive DNS servers.