Aria Suite Lifecycle certificate replacement fails for Aria Operations for Logs due to FQDN mismatch.

Products

• VCF Operations
• VCF Operations/Automation (formerly VMware Aria Suite)

Issue/Introduction

• Certificate replacement precheck in Aria Suite Lifecycle (vRSLCM) fails for Aria Operations for Logs (vAOL/vRLI).
  
  
• Manual certificate replacement via the Aria Operations for Logs UI fails with "Failed to save certificate."
  
  
• Aria Operations for Logs nodes are out of sync or showing "Inconclusive" health status.

Environment

VMware Aria Operations for Logs 8.18.x

VMware Aria Suite Lifecycle Manager 8.18.x 

Cause

The appliance was configured with a "short name" rather than a Fully Qualified Domain Name (FQDN).

This is often driven by vCenter vApp options pushing short names to the appliance OS, which conflicts with certificate SAN requirements during vRSLCM operations.

Resolution

Please backup the environment prior following the below changes. 

1. Power off all Aria Operations for Logs nodes.
2. In vCenter, navigate to each VM > Configure > Settings > vApp Options.
3. Edit the hostname property to reflect the FQDN (e.g., logs01.example.com) instead of the short name.
4. Power on the Primary node first. Verify the hostname persists by running hostname -f.
5. Power on the remaining worker nodes.
6. Perform a sequential reboot of the cluster to make sure the changes are persistent. ( If required, Optional )
7. Log into Aria Suite Lifecycle Manager and perform an Inventory Sync for the Aria Operations for Logs environment to ensure it captures the updated FQDN.
8. Proceed with the certificate import or renewal task.

Additional Information

Hostname configurations in VMware Aria Operations for Logs 8.14+ (KB 315950)