Workload Cluster Addition Fails with NSX IP Pool Path Invalid Error
search cancel

Workload Cluster Addition Fails with NSX IP Pool Path Invalid Error

book

Article ID: 434850

calendar_today

Updated On:

Products

VMware SDDC Manager VMware NSX

Issue/Introduction

Adding a workload cluster in SDDC Manager fails. Verification in the NSX UI shows the IP pool is created, but the API path for the pool contains an unexpected randomized string appended to the name (e.g., /infra/ip-pools/<IP Pool Name>30B1nPWQ00).

Message: IP address pool spec validation failed with errors []

Cause: Failed to validate the IP address pool

A review of the NSX Manager syslogs reveals the following errors indicating a path validation failure:

<REDACTED_HOSTNAME> NSX 6331 - [nsx@6876 audit="true" comp="nsx-manager" level="INFO" reqId="645c3134-1552-4b12-bac6-eccea7adf25c" subcomp="manager" username="admin"] UserName="admin", Src="<REDACTED_IPS>", ModuleName="PolicyIpam", Operation="ListIpAddressPoolSubnets", Operation status="failure", New value=["<IP Pool Name>" {"include_mark_for_delete_objects":false,"page_size":1000}]

 

<REDACTED_HOSTNAME> NSX 6331 SYSTEM [nsx@6876 audit="true" comp="nsx-manager" level="INFO" subcomp="manager"] UserName:'admin' ModuleName:'Policy' Operation:'GET@/api/v1/infra/ip-pools/<IP Pool Name>/ip-subnets' Operation status: 'failure' Error: The path=[/infra/ip-pools/<IP Pool Name>] is invalid

Environment

VMware Cloud Foundation 5.2.1

VMware NSX 4.2.2.1

Cause

The error occurs because the newly created IP pool was assigned the exact same display name as an already existing IP pool. To enforce internal uniqueness, NSX appends a randomized suffix to the backend API path. This mismatch between the expected standard path and the newly modified backend path causes SDDC Manager validation to fail during the workload cluster addition.

Resolution

  1. Log in to the NSX Manager UI.
  2. Locate the IP pool that was recently created for the workload cluster addition.
  3. Delete the IP pool.
  4. Recreate the IP pool, ensuring it is assigned a strictly unique display name that does not match any existing or previously existing pools.
  5. Retry the workload cluster addition workflow in SDDC Manager.