NSX resources with policy IDs containing special characters are not supported in vSphere Supervisor

Products

• VMware vSphere Kubernetes Service

Issue/Introduction

When configuring or utilizing vSphere Supervisor, administrators may experience issues or errors when attempting to use certain NSX resources, such as Virtual Private Clouds (VPCs) or Subnets.

This specifically occurs if the NSX resource's policy ID contains any of the following special characters:

• : (colon)

• ? (question mark)

• # (hashtag/pound sign)

• [ (left bracket)

• ] (right bracket)

Environment

 

• VMware vSphere Supervisor 9.1

• VMware NSX

 

Cause

The vSphere Supervisor does not currently support parsing or integrating with NSX policy IDs that include these specific special characters.

Resolution

There is currently no patch to allow the use of these characters. To work around this issue and ensure successful integration with the Supervisor, you must avoid using these special characters in your naming conventions.

Steps to resolve:

1. Identify any required NSX resources (e.g., VPCs, Subnets) that have policy IDs containing :,?, #, [, or ].

2. Recreate or rename the NSX resources using policy IDs that do not contain any of the unsupported special characters.

3. Reattempt the integration or deployment with the vSphere Supervisor using the newly created, compliant NSX resources.

Issue is documented in Release notes