Error: VCF Installer overwrites custom JSON IP Pool and vSAN Datastore naming (VCF 9.1.0)

Products

• VMware SDDC Manager / VCF Installer

Issue/Introduction

When deploying VMware Cloud Foundation (VCF) 9.1.0 using an external JSON file as the initial payload, the VCF Installer ignores custom naming and descriptions provided in the ipAddressPoolSpec and vsanDatastoreSpec objects.

Observed symptoms include:

• Custom IP Address Pool names and descriptions are reverted to autogenerated values (e.g., <cluster-name>-tep01).
• vSAN Datastore names provided in the JSON are appended with a "01" suffix (e.g., ds-vsan becomes ds-vsan01).
• The custom naming is visible in the initial JSON but is overwritten after navigating through the interactive installer wizard pages.

Environment

• VMware Cloud Foundation 9.1.0.x
• VCF Installer build 9.1.0.x
• Interactive Deployment with JSON "Initial Payload"

Cause

This is a known issue where the VCF Installer wizard logic fails to persist custom naming specs from the input JSON for specific management domain components.

Resolution

This issue is currently under investigation by Engineering. Subscribe to this article to receive updates on the fix status. See Subscribe to updates for a Knowledge Base article for instructions.

 

Workaround:

To maintain custom naming conventions, perform the following manual workarounds after the deployment completes:

Rename vSAN Datastores

1. 1. Log in to the vSphere Client.
   2. Navigate to Storage > Select the vSAN Datastore.
   3. Right-click the datastore and select Rename.

Rename IP Address Pools

1. 1. Log in to the NSX Manager UI.
   2. Navigate to Networking > IP Address Pools.
   3. Edit the specific pool (e.g., <cluster-name>-tep01) and update the Name and Description fields to match your requirements.

Additional Information

• NSX TEP IP Pool visibility and naming restrictions (KB 439852)
• Renaming vSAN datastores in VCF 9 (KB 421995)