"vCenter task auto-configuration failed for the following host" email alert is triggered from Aria Operations for Logs

Products

• VCF Operations/Automation (formerly VMware Aria Suite)

Issue/Introduction

• The following alert triggered daily:  "vCenter task auto-configuration failed for the following host"

• At the time the alert is triggered, running the following command from the vCenter Server Appliance to verify connectivity to Aria Operations for Logs: curl -v telnet://TargetFQDN.in:443, indicates a failure to establish a connection: curl -v telnet://TargetFQDN.in:443
  
  
  
  
  
• The below log snippet is found in the /storage/core/loginsight/var/systemalert.log, the error indicates that vCenter cannot reliably establish an HTTPS (443) connection to Aria Operations for Logs during auto-configuration triggering the alert.
  
  {"Timestamp":"yyyy-mm-dd T hh:mm:ss","Data":{"AlertId":"vCenter auto-configuration failed","Name":"vCenter auto-configuration failed","Description":"vCenter task auto-configuration failed for the following host:\n\vCenterFQDN\n{\"key\":\"com.vmware.loginsight.vsphere.config.VimVsphereConfigurer.cannotConnect\",\"params\":[]}\n\nThis message was generated by your VMware Aria Operations for Logs installation, visit the <a href='https://docs.vmware.com/en/VMware-Aria-Operations-for-Logs/index.html'>Documentation Center</a> for more information.","TriggerTime":"yyyy-mm-dd T hh:mm:ss"},"AutoClearTimeoutSeconds":-1}

Environment

Aria Operations for Logs 8.18.x

Cause

The issue occurs due to intermittent network connectivity interruptions between vCenter Server and Aria Operations for Logs.

 

Resolution

To resolve this issue, check with the internal networking team to identify and resolve any network, routing, or firewall issues that are blocking communication.

After the connectivity between the vCenter Server and Aria Operations for Logs is restored, the vCenter alert will no longer trigger.

Additional Information

Related KB article: 393613