Aria Suite Lifecycle: Inventory Sync for Aria Operations for Networks fails at 'Verify Ssh Connection' Stage Due to Collector Logout Issue

Products

• VMware vRealize Suite Lifecycle Manager 8.x
• VCF Operations for Networks

Issue/Introduction

When attempting to perform an Product Inventory Sync for Aria Operations for Networks (formerly vRealize Network Insight, or vRNI) using Aria Suite Lifecycle (vRSLCM), the request gets stuck indefinitely at Stage 1 - Verify Ssh Connection.

• Symptom: The sync request shows no progress, no timeout, and no error message, remaining stuck at Stage 1 - Verify Ssh Connection for many hours.

• Context: This issue is typically observed when preparing to upgrade Operations for Networks and the inventory sync is a prerequisite step.

• Relevant Logs: The vmware_vrlcm.log may show successful execution of commands but the task fails to complete due to a subsequent failure in the SSH session cleanup.

Environment

Aria Suite Lifecycle Manager 8.x

Aria Operations for Networks 6.x

Cause

The root cause is a failure in the logout procedure on the Operations for Networks appliance, specifically on the Collector Node, after Aria Suite Lifecycle executes an SSH command (like show-version) for validation.

The connection attempt itself is successful, but the script used by LCM to collect data and then close the session encounters an error on the target appliance, specifically:

name ‘pid’ is not defined

Because the logout command fails to complete successfully, the Verify Ssh Connection stage in Aria Suite Lifecycle never receives the final success signal and remains indefinitely stuck.

Resolution

The resolution involves addressing the underlying issue on the Aria Operations for Networks side, for example an issue with the Collector Node configuration or deployment causing the logout failure.

1. Identify the problematic Operations for Networks Collector Node.

2. Replace or Redeploy the impacted Collector Node.

3. Restart the Product Inventory Sync from the Aria Suite Lifecycle Manager UI after the Collector Node is successfully replaced/repaired and is operating normally.