After upgrade to 30.2.1 , NSX-T the cloud may go down with the status "Valid Vcenter config doesn't exist in cloud".

Products

• VMware Avi Load Balancer

Issue/Introduction

After upgrade to 30.2.1 , NSX-T the cloud may go down with the status "Valid Vcenter config doesn't exist in cloud".

Environment

- NSX-T cloud

Cause

- This bug is because of the change in vCenter resolution from NSX workflow.
- vCenter validation fails here because the FQDN returned from NSX does not match with the vCenter IP configured in the Cloud config on Avi. 
 

Resolution

- Since the vCenter field is immutable, there is no workaround for this issue.
- This issue has been fixed in a patch on 30.2.1 and has also been addressed in the later GA releases.
- Bug ID: AV-206679
- Fix Versions: 30.2.1-2p1, 30.2.2
- The recommendation is to apply the latest 2px on top of 30.2.1, since patches are incremental in Avi.

Additional Information

- To verify the issue, confirm the following.
- List the compute-managers from the NSX manager configured in the cloud using the API call below:

/api/v1/fabric/compute-managers

- The output will have the vCenter server IP/FQDN. For example:

{
    "results": [
        {
            "server": "example-domain.in.org",
            "origin_type": "vCenter",
            "credential": {
                "thumbprint": "<>",
                "credential_type": "UsernamePasswordLoginCredential"
            },
........

- If the server field has a FQDN and the cloud configuration on Avi has an IP for the vCenter field, this issue will be hit.