"Incoming request (v22.1.5) has field (graceful_hm_down_disable_timeout) introduced in later versions(v30.2.1)." error in VMware Cloud Director after upgrading NSX Advanced Load Balancer (AVI)

Products

• VMware Cloud Director

Issue/Introduction

Customer recently upgraded the NSX Advanced Load Balancer (AVI) Controller from an older version (e.g., 22.1.5) to a newer version (e.g., 30.2.6).

Create AVI cluster failed with error:

• Incoming request (v22.1.5) has field (graceful_hm_down_disable_timeout) introduced in later versions(v30.2.1).

Environment

VMware Cloud Director 10.6.1

NSX Advanced Load Balancer 30.2.6

Cause

This issue occurs due to a mismatch between the actual AVI Controller version and the version cached inside the VCD database.

When you upgrade the AVI Controller out-of-band (directly from the AVI UI/CLI), VCD is not automatically notified of the version change. VCD continues to construct REST API payloads using the older API context (e.g., v22.1.5). However, newer VCD releases inject newer parameters (like graceful_hm_down_disable_timeout) into the payload. The AVI Controller's strict API schema validation rejects the request because the older API version context (v22.1.5) does not recognize fields introduced in later versions (v30.2.1).

Resolution

To resolve this issue, you must force VMware Cloud Director to re-authenticate and refresh the version information of the registered AVI Controller.

1. Log in to the VMware Cloud Director Provider Portal as a System Administrator.
2. From the top navigation menu, go to Infrastructure Resources.
3. In the left pane, under NSX-T ALB, click on Controllers.
4. Select the affected AVI Controller from the list and click Edit.
5. Re-enter the admin credential and click Save.
6. This action forces VCD to establish a new connection to the AVI Controller, perform a version handshake, and update its internal database with the new AVI version (e.g., 30.2.6).
7. Verify the version of the Controller shows correct (e.g., 30.2.6).
8. Retry the load balancer configuration task; it should now complete successfully using the correct API version context.