This article provides steps to validate "Edge Cluster Validation" failure during creation phase.The detailed error shown in SDDC UI reads as, "The attempted functionality EDGE_CLUSTER_VALIDATION is not supported in the current system state
. Failed to retrieve context id with request com.vmware.evo.sddc.rest.client.MustReadRequestWrapper"
YYYY:MM:DDTHH:MIN DEBUG [vcf_dm,18af3bbbe358408b,6b75] [c.v.v.f.t.i.FunctionalityToggleApiFilter,http-nio-127.0.0.1-7200-exec-5] Getting domain context id for functionality
YYYY:MM:DDTHH:MIN DEBUG [vcf_dm,18af3bbbe358408b,6b75] [c.v.v.d.f.DMFunctionality,http-nio-127.0.0.1-7200-exec-5] Getting domain context id for request body type class com.vmware.vcf.rest.api.model.v1.edgeclusters.EdgeClusterCreationSpec
YYYY:MM:DDTHH:MIN DEBUG [vcf_dm,18af3bbbe358408b,6b75] [c.v.v.d.f.h.EdgeClustersPostHandler,http-nio-127.0.0.1-7200-exec-5] Getting domain context for EDGE CLUSTERS POST with request: {"edgeClusterName":"example_cluster_name","edgeClusterType":"NSX-T
"edgeRootPassword":"*****","edgeAdminPassword":"*****","edgeAuditPassword":"*****","edgeFormFactor":"LARGE", "tier0ServicesHighAvailability":"ACTIVE_ACTIVE", "mtu":9000,"tier0RoutingType":"STATIC","edgeNodeSpecs" :[{"edgeNodeName":"example_edge_node_name",
"managementIP":"192.168.0.0","managementGateway":"192.168.0.1","edgeTep1IP":"192.168.0.2","edgeTep2IP":"192.168.0.3", "edgeTepGateway":"192.168.0.4","edgeTepVlan":####,"clusterId":"428###-####-####-##eb","interRackCluster":false,"uplinkNetwork":
[{"uplinkVlan":####,"uplinkInterfaceIP":"192.168.0.5"},{"uplinkVlan":####, "uplinkInterfaceIP":"192.168.0.6"}]},{"edgeNodeName":"example_edge_node_name","managementIP":"192.168.0.11",
"managementGateway":"192.168.0.1","vmManagementPortgroupVlan":"","vmManagementPortgroupName":"","edgeTep1IP":"192.168.0.7","edgeTep2IP":"192.168.0.8","edgeTepGateway":"192.168.0.4","edgeTepVlan":####,"clusterId": "428###-####-####-##eb","interRackCluster":false,
"uplinkNetwork"::"192.168.0.9"}, [{"uplinkVlan":####,"uplinkInterfaceIP"{"uplinkVlan":####,"uplinkInterfaceIP":"192.168.0.10"}]}],"tier0Name":"example_cluster_name_t0","tier1Name":"example_cluster_name_t1","edgeClusterProfileType":"DEFAULT"}
YYYY:MM:DDTHH:MIN ERROR [vcf_dm,18af3bbbe358408b,6b75] [c.v.v.d.f.DMFunctionality,http-nio-127.0.0.1-7200-exec-5] Exception thrown when getting domain context id from request.
com.vmware.evo.sddc.common.core.error.InvalidInputException: Failed to retrieve the domain context id with request com.vmware.evo.sddc.rest.client.MultiReadRequestWrapper@#####.
SDDC 5.x
vmManagementPortgroupVlan
":"","vmManagementPortgroupName
":" has invalid character as ':
'. This leads to an exception thrown by SDDC during its validation of the required clusterspec. In a rare scenario, when SDDC is running on VxRail environment, the null value is replaced by invalid character.Following workaround steps can be taken to remediate the issue
UI Method:
Or
document.querySelector('[id="edgeClusterNodeDetailsPageCluster"]').value = null;
Once the combobox is cleared, the user can select the single cluster again which will lead to proper spec file generation.API Method:
Please refer to Edge Cluster creation via API for required fields.