Creating / Deleting VI workload domain fails with error "Multiple rings found in topology, should be exactly one ring"
search cancel

Creating / Deleting VI workload domain fails with error "Multiple rings found in topology, should be exactly one ring"

book

Article ID: 336765

calendar_today

Updated On:

Products

VMware Cloud Foundation

Issue/Introduction

Creating workload domain fails at subtask "Validate the Single Sign-On (SSO) Ring Topology"

  • Error "Multiple rings found in topology, should be exactly one ring. Rings found inside topology"

  • Log file /var/log/vmware/vcf/domainmanager/domainmanager.log will show entries similar to:

2023-03-21T12:27:42.308+0000 DEBUG [vcf_dm,c4bcb8da562944ac,eb2b] [c.v.v.v.s.s.c.SsoDataModelConvertor,dm-exec-12]  Converted topogy: [{"nodeId":"vcenter-1.vrack.vsphere.local","replicationPartners":[],"type":"PSC_EXTERNAL"}]
2023-03-21T12:27:42.309+0000 DEBUG [vcf_dm,c4bcb8da562944ac,eb2b] [c.v.v.v.s.s.SsoRingTopologyServiceImpl,dm-exec-12]  Found topology {"nodes":[{"nodeId":"vcenter-1.vrack.vsphere.local","replicationPartners":[],"type":"PSC_EXTERNAL"}]}
2023-03-21T12:27:42.310+0000 DEBUG [vcf_dm,c4bcb8da562944ac,eb2b] [c.v.v.v.s.s.SsoRingTopologyServiceImpl,dm-exec-12]  Found management nodes []
2023-03-21T12:27:42.310+0000 DEBUG [vcf_dm,c4bcb8da562944ac,eb2b] [c.v.v.v.s.s.SsoRingTopologyServiceImpl,dm-exec-12]  Topology after removing replications between management vCenters {"nodes":[]}
2023-03-21T12:27:42.311+0000 DEBUG [vcf_dm,c4bcb8da562944ac,eb2b] [c.v.v.v.s.s.SsoRingTopologyServiceImpl,dm-exec-12]  Found following rings []
2023-03-21T12:27:42.311+0000 DEBUG [vcf_dm,c4bcb8da562944ac,eb2b] [c.v.v.v.s.s.SsoRingTopologyServiceImpl,dm-exec-12]  Found following rings with known nodes: []
2023-03-21T12:27:42.317+0000 ERROR [vcf_dm,c4bcb8da562944ac,eb2b] [c.v.e.s.o.model.error.ErrorFactory,dm-exec-12]  [LCC9EK] SSO_RING_TOPOLOGY_MULTIPLE_RINGS Multiple rings found in topology, should be exactly one ring. Rings found inside topology: []
com.vmware.evo.sddc.orchestrator.exceptions.OrchTaskException: Multiple rings found in topology, should be exactly one ring. Rings found inside topology: []
        at com.vmware.vcf.vimanager.fsm.actions.HealthCheckRingTopologyVc70Action.execute(HealthCheckRingTopologyVc70Action.java:59)
        at com.vmware.vcf.vimanager.fsm.actions.HealthCheckRingTopologyVc70Action.execute(HealthCheckRingTopologyVc70Action.java:24)
        at com.vmware.evo.sddc.orchestrator.platform.action.FsmActionState.invoke(FsmActionState.java:62)
        at com.vmware.evo.sddc.orchestrator.platform.action.FsmActionPlugin.invoke(FsmActionPlugin.java:159)
        at com.vmware.evo.sddc.orchestrator.platform.action.FsmActionPlugin.invoke(FsmActionPlugin.java:144)
        at com.vmware.evo.sddc.orchestrator.core.ProcessingTaskSubscriber.invokeMethod(ProcessingTaskSubscriber.java:400)
        at com.vmware.evo.sddc.orchestrator.core.ProcessingTaskSubscriber.processTask(ProcessingTaskSubscriber.java:520)
        at com.vmware.evo.sddc.orchestrator.core.ProcessingTaskSubscriber.accept(ProcessingTaskSubscriber.java:124)
        at jdk.internal.reflect.GeneratedMethodAccessor513.invoke(Unknown Source)
        at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
        at java.base/java.lang.reflect.Method.invoke(Method.java:566)
        at com.google.common.eventbus.Subscriber.invokeSubscriberMethod(Subscriber.java:88)
        at com.google.common.eventbus.Subscriber$1.run(Subscriber.java:73)
        at org.springframework.cloud.sleuth.instrument.async.TraceRunnable.run(TraceRunnable.java:68)
        at org.springframework.cloud.sleuth.instrument.async.TraceRunnable.run(TraceRunnable.java:68)
        at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
        at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
        at java.base/java.lang.Thread.run(Thread.java:829)

  • Error on SDDC-UI:

    Description: Validate the Single Sign-On (SSO) Ring Topology
    Progress Messages: Multiple rings found in topology, should be exactly one ring. Rings found inside topology: []Error
    Message: Multiple rings found in topology, should be exactly one ring. Rings found inside topology: []

Environment

VMware Cloud Foundation 4.x

Cause

The root cause of this issue is that the LDU attribute value for the vCenter was incorrectly set, which caused the topology service to report it as an external PSC. This led VCF to incorrectly determine that forming a Ring topology was not possible. 

If customer has previously performed a cross-domain repoint to create replication partners, decommission stale vCenters, or even conducted a self-repoint, during a cross-domain repoint, a new LDU GUID is generated and applied to the domain controller account/object.

When the topology service (topologysvc) attempts to detect the appliance type, it will identify the node as PSC_EXTERNAL instead of VCSA_EMBEDDED because the LDU GUID no longer matches the Node ID parameter in the vCenter Server Lookup Service registration.

Resolution

If you encounter the symptoms outlined above, please contact Broadcom Technical Support for further assistance, as the resolution involves modifying vmdir database instance, which should be performed with caution.

Additional Information

Get Node type from SDDC Manager: 

curl -u 'Administrator@<SSO-Domain>:<SSO-Passwd>' -X POST -k https://<VC-FQDN>:443/rest/com/vmware/cis/session
curl --insecure --request GET --url https://<VC-FQDN>/rest/vcenter/topology/nodes --header 'vmware-api-session-id:<Session ID output from above command>'

 

Powered by Wolken Software