Vcenter/NSX Cloud status is in failed status with Bad Gateway/Forbidden Error

Products

• VMware Avi Load Balancer

Issue/Introduction

After Upgrading the Avi controller to 30.2.2, cloud status is failing with "Bad Gateway" Error 

[admin:##-##-##-##]: > show cloud <cloud name> status 
+-------+-----------------------------+
| Field | Value                       |
+-------+-----------------------------+
| state | CLOUD_STATE_FAILED          
| reason| Head 				BAD Gateway
+-------+-----------------------------+

>> Adding new Vcenter/NSX cloud also fails with "Bad Gateway Error"

Other Possible Errors due to Proxy Configuration:

>> Cloud status is down with "HEAD <vcenter/NSX URL > Service Unavailable error"

 

 

Environment

Cloud: Vcenter/NSX cloud

Version: 30.2.1 & 30.2.2 & 30.2.3

Cause

• Prior to Avi Load Balancer 30.2.1 version proxy configuration was used to connect to All clouds(except Vcenter/NSX) and internet reachability.
• From AVI Load Balancer version 30.2.1 a new feature is added to use proxy configuration(if configured) to connect to vcenter/NSX cloud. This new feature is causing cloud status to down.

From the controller CLI, verify if the any proxy configuration is present using below command.

Command: show systemconfiguration 

[admin:##-##-##-##]: > show systemconfiguration | grep "proxy"

search for "proxy_configuration" string from the command output.

"proxy_configuration": {
                                "host": "abc.com",
                                "port": 443
                        }

 

Resolution

• As a workaround we can remove proxy configuration from the Avi controller CLI and check if the cloud status turns green.
• Customer can check from the proxy side to determine why the traffic is not forwarded to the vCenter/NSX devices.

Steps to remove proxy configuration:

>> Please run below commands to remove the proxy_configuration.

[admin:##-##-##-##]: > configure systemconfiguration
[admin:##-##-##-##]: systemconfiguration> no proxy_configuration
[admin:##-##-##-##]: systemconfiguration> save

Additional Information

• Additionally This issue is fixed in 31.2.1 from AVI side.