Multiple "vCenter auto-configuration failed" email alert notifications seen after Aria Operations for Logs upgrade

Products

• VCF Operations/Automation (formerly VMware Aria Suite)

Issue/Introduction

After upgrading to Aria Operations for Logs 8.18.6, a "vCenter auto-configuration failed/vCenter task auto-configuration failed for the following hosts" alert is triggered daily.

Symptoms include:

• Alerts occurring at the same time every night.

• The /storage/core/loginsight/var/runtime.log contains the following errors:

  • [Date & Time] ["ScheduledPluginServiceScheduledTask-thread-1"/##.##.##.## ERROR] [com.vmware.loginsight.config.VsphereCredential] [Failed to decrypt:] javax.crypto.BadPaddingException: Given final block not properly padded. Such issues can arise if a bad key is used during decryption.

  • [Date & Time]["ScheduledPluginServiceScheduledTask-thread-1"/##.##.##.## INFO] [com.vmware.loginsight.notifications.AlertNotifier] [Sending alert notification for: vCenter auto-configuration failed]

  • [Date & Time]["ScheduledPluginServiceScheduledTask-thread-1"/##.##.##.## INFO] [com.vmware.loginsight.notifications.AlertNotifier] [Alert recently sent, skipping notification: vCenter auto-configuration failed]

• vCenter integrations show as "Collecting" and no network issue is observed.

Environment

Aria Operations for Logs 8.18.x

Cause

This occurs when a cluster node fails to synchronize the new encryption key generated during the upgrade process. When the node attempts to run scheduled vCenter configuration tasks, it uses an incorrect key to decrypt the vSphere credentials, resulting in a decryption failure.

Resolution

 

1. Restart Services: SSH to the node reporting the error and run: systemctl restart loginsight

2. Verify Sync: Ensure that the loginsight-config.xml### file located in /storage/core/loginsight/config/ is synchronized across the cluster nodes. The configuration generation number (represented by ###) on the node in question should match the highest version number found on the other cluster nodes.

3. Update Credentials: If the error persists, navigate to Integrations > vSphere, edit the vCenter connections, and re-type the passwords to force a fresh encryption cycle.