Deployment of New Edge Cluster via VCF SDDC Manager Stuck | SDDC Error: Update VLAN Portgroup for Vds {0} in Inventory failed

Products

• VMware Cloud Foundation

Issue/Introduction

The deployment of a new Edge Cluster using VMware Cloud Foundation (VCF) Single Deployment and Design (SDDC) Manager is stuck, displaying an error: "Update VLAN Portgroup for Vds {0} in Inventory failed." The issue stems from a duplicate entry causing a validation failure due to multiple VM_MANAGEMENT port groups being found for the cluster.

Observe the following error stack within the SDDC Workflow:

Cause: Duplicate key <portgroup_name> (attempted merging values class PortGroup { name: <portgroup_name> transportType: PUBLIC type: EARLY_BINDING vlanId: 0 mtu: 0 activeUplinks: [uplink1] standbyUplinks: [uplink2] sourceId: dvportgroup-xx } and class PortGroup { name: <portgroup_name> transportType: VM_MANAGEMENT type: EPHEMERAL vlanId: xxxx mtu: 0 activeUplinks: [uplink1] standbyUplinks: [uplink2] sourceId: dvportgroup-xx })

Observe this failure prior to the Validation of the NSX Edge Deployment and after filling out the necessary information:

"Failed to trigger validation operation. Something went wrong. Please retry or contact the service provider and provide the reference token."

Observe the following log entries in the /var/log/vmware/vcf/domainmanager/domainmanager.log:

ERROR [vcf_dm,0000000000000000,0000] [o.a.c.c.C.[.[.[.[dispatcherServlet],http-nio-127.0.0.1-7200-exec-7]  Servlet
.service() for servlet [dispatcherServlet] in context with path [/domainmanager] threw exception [Request processing failed: java.lang.IllegalA
rgumentException: Multiple VM_MANAGEMENT portgroup(s) found for cluster] with root cause java.lang.IllegalArgumentException: Multiple VM_MANAGEMENT portgroup(s) found for cluster

Environment

VCF SDDC Manager 5.x

Cause

The deployment was halted because of duplicate entries in both the Virtual Distributed Switch (VDS) table and NSX Edge Cluster configuration, specifically regarding the "<vi-wld-portgroup-name>" port group. The issue was caused by manually creating a VI-WLD port group outside of SDDC Manager workflows.

Resolution

To resolve this issue, please reach out to Broadcom Support for further assistance.