During upgrade of VMware Aria Automation from version 8.18.x to VCFA 9.0.x, Aria Automation network information fails to populate in Fleet Manager 9.0.x

Products

• VCF Operations/Automation (formerly VMware Aria Suite)

Issue/Introduction

When importing VMware Aria Automation version 8.18.x from Aria Suite Life Cycle Manager into Fleet Management as part of a VCF Automation 9.0 upgrade (VCFA Import), the network properties for some Aria automation nodes may not populate correctly.

Specifically, the network information is missing for the primary and tertiary Aria Automation nodes in the Fleet Manager UI, while the secondary node network information is present.

Environment

VCF Automation 9.0.x

Cause

The network information fails to populate for two of the AA nodes (primary) during the import process due to an issue where the node types were not correctly identified or synchronized in the VCF Ops Fleet Manager database.

 

Resolution

Resolution: Broadcom Engineering team is aware of the issue and this will be fixed in future versions.

Workaround:

The workaround involves swapping the node types of the affected primary and a working secondary node within the VCF Fleet manager database to enable the upgrade to proceed.

The resolution requires a direct database modification on the VCF Fleet manager  appliance and should be performed with caution. Before proceeding, it is critical to take a snapshot of the VCF Fleet Manager appliance.

1. Take a snapshot of the VCF Fleet Manager appliance.
2. SSH to the VCF Fleet Manager appliance as the root user.
3. Log in to the PostgreSQL database using the following commands:

   cd /opt/vmware/vpostgres/current/bin
   su postgres
   ./psql -d vrlcm

4. Identify the Product VMID of the Aria Automation product using the query:

   select * from vm_lcops_product where id='vra';

5. Retrieve the details of all Aria Automation nodes using the product_vmid obtained in the previous step. Replace <VMID-of-AA (Aria Automation)-product> with the actual ID:

   select * from vm_lcops_product_nodes where product_vmid='<VMID-of-AA-product>';

6. Swap the node types of the current primary (vrava-primary) and the working secondary (vrava-secondary) nodes by updating the database. The example below shows a swap using placeholder VMIDs. Replace the placeholder VMIDs with the actual VMIDs of your primary and working secondary nodes.

   update vm_lcops_product_nodes set type='vrava-secondary' where vmid='[vmid of current primary node]';
   update vm_lcops_product_nodes set type='vrava-primary' where vmid='[vmid of current secondary node with network info]';

7. Verify the swap: Check the UI and components page. The node that was designated as the secondary should now show the network information as the new primary node.

8. Trigger the upgrade of the Aria Automation environment. Do not perform an inventory sync before triggering the upgrade.