VPC on NSX is not syncronized to Avi Load Balancer

Products

• VMware Avi Load Balancer

Issue/Introduction

A new VPC created on NSX is not visible on Avi under the required tenant. 

 

Environment

Avi Load Balancer version 30.x, 31.1.1

NSX cloud with VPC mode enabled

Cause

A cloud update operation fails due to a duplication conflict related to a Virtual Private Cloud (VPC) and its associated Virtual Routing and Forwarding (VRF) context on Avi. After the failure, subsequent VPC discoveries and creations are unable to synchronize successfully. This impacts all new VPCs, regardless of tenant.

 Flow that can lead to the issue: 

 

• A new VPC (V1) is created under a project (P1) on the network platform.

• As part of this creation, a corresponding VRF for V1 is automatically created in the Avi cloud configuration, referencing the same project path.

• The VPC (V1) is later deleted from the project (P1) on the network platform.

• Although the VPC is removed from the network platform, the associated entry is not automatically removed from the Avi cloud configuration.

• The same VPC (V1) is subsequently re-created manually on the network platform.

• During the next discovery cycle, the system attempts to update the cloud configuration but detects that the VPC entry already exists in the cloud database. This results in a unique constraint violation, causing the cloud update to fail. An error similar to the following is observed in the cloud connector logs:
  
  "Field check for tier1_lrs failed: Unique constraints tier1_lr_id has duplicated value: /orgs/<org>/projects/<project_name>/vpcs/<vpc_name>

Resolution

There are two workarouds for the issue: 

• • either, restart cloudconnetorgo service.
    Use the below set of commands respectively to stop and start the cloudconnectorgo service after logging in to the cli of leader controller node: 
    

    # sudo systemctl stop cloudconnectorgo.service
# sudo systemctl start cloudconnectorgo.service
    

  • or, delete the error'd vpc from the cloud. This can be done by editing the required NSXT cloud under infrastructure > clouds > edit required cloud. Sample screenshot below for removing the error'd vpc: 
    
    

Fix: Upgrade to version 31.1.2 or later to benefit from the built-in auto-cleanup capability.