Failed to fetch topology from all known nodes: [FQDN, FQDN, ...] in Validate the Single Sign-On (SSO) Ring Topology task
search cancel

Failed to fetch topology from all known nodes: [FQDN, FQDN, ...] in Validate the Single Sign-On (SSO) Ring Topology task

book

Article ID: 406668

calendar_today

Updated On:

Products

VMware SDDC Manager

Issue/Introduction

  • Unable to delete workload domain from SDDC Manager.
  • SDDC Manager UI shows following error.

 

domainmanager.log

2025-08-05T04:13:46.736+0000 DEBUG [vcf_dm,9ef1c81a71cc355f,36d5] [c.v.v.v.s.s.e.SsoRestCommandExecutor,dm-exec-19]  Creating new session to SSO host <host name> with user [email protected]
2025-08-05T04:13:46.880+0000 WARN  [vcf_dm,9ef1c81a71cc355f,36d5] [c.v.v.v.s.s.SsoRingTopologyServiceImpl,dm-exec-19]  Unable to fetch topology from <host name>, continuing with next node.
2025-08-05T04:13:46.880+0000 DEBUG [vcf_dm,9ef1c81a71cc355f,36d5] [c.v.v.v.s.s.SsoRingTopologyServiceImpl,dm-exec-19]  Found topology null
2025-08-05T04:13:46.880+0000 ERROR [vcf_dm,9ef1c81a71cc355f,36d5] [c.v.e.s.o.model.error.ErrorFactory,dm-exec-19]  [LAGFH2] SSO_RING_TOPOLOGY_FETCH_FAILED_FROM_NODES Failed to fetch topology from all known nodes: [FQDN, FQDN, ...].
com.vmware.evo.sddc.orchestrator.exceptions.OrchTaskException: Failed to fetch topology from all known nodes: [FQDN, FQDN, ...].
        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.GeneratedMethodAccessor413.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)
2025-08-05T04:13:46.881+0000 DEBUG [vcf_dm,9ef1c81a71cc355f,36d5] [c.v.e.s.o.c.ProcessingTaskSubscriber,dm-exec-19]  Collected the following errors for task with name HealthCheckRingTopologyVc70Action and ID <ID>: [ExecutionError [errorCode=null, errorResponse=LocalizableErrorResponse(messageBundle=com.vmware.vcf.vimanager.error.messages)]]

 

lcm-debug.log

2025-08-05T03:58:32.967+0000 DEBUG [vcf_lcm,76384702beed3e53,b184] [c.v.e.s.l.a.i.i.HardwareSupportClientImpl,http-nio-127.0.0.1-7400-exec-4] Fetching cluster upgradables details using Personality Image Manager for the domain <UUID> with vCenter version 7.0.3.01100-20845200
2025-08-05T03:58:32.971+0000 INFO  [vcf_lcm,76384702beed3e53,b184] [c.v.v.s.https.vapi.VapiClientFactory,http-nio-127.0.0.1-7400-exec-4] Creating new session on <host name> for [email protected]
2025-08-05T03:58:33.073+0000 ERROR [vcf_lcm,76384702beed3e53,b184] [c.v.e.s.l.a.i.i.HardwareSupportClientImpl,http-nio-127.0.0.1-7400-exec-4] Exception occurred while loading the Hardware Support Info for the domain <UUID>
com.vmware.vapi.std.errors.ServiceUnavailable: ServiceUnavailable (com.vmware.vapi.std.errors.service_unavailable) => {
    messages = [LocalizableMessage (com.vmware.vapi.std.localizable_message) => {
    id = com.vmware.vapi.endpoint.failedToLoginMaxUserSessionCountReached,
    defaultMessage = User session count is limited to 550. Existing session count is 550 for user [email protected].,
    args = [550, 550, [email protected]],
    params = <null>,
    localized = <null>
}],
    data = <null>,
    errorType = SERVICE_UNAVAILABLE
}

 

 

Environment

SDDC Manager

Cause

The issue occurs when attempting to delete a Workload Domain, but the operation fails before the deletion process begins. This is because SDDC Manager is unable to establish a new session with one or more vCenter Servers, as the user account used to connect—such as [email protected]—has already reached the maximum session limit of 550.

In environments configured with Enhanced Linked Mode (ELM), SDDC Manager performs API calls to each vCenter Server to retrieve node information prior to initiating the deletion process. These API calls require creating new sessions, and if the session count limit has already been exceeded, the precheck or validation step fails immediately.

Resolution

To release the excess sessions and allow the operation to proceed, restart the vapi-endpoint service (and related services) on each vCenter Server managed by the SDDC Manager.

  1. SSH into each vCenter Server using the root user.

  2. Run the following commands in a bash shell:

 
service-control --stop vmware-infraprofile && service-control --start vmware-infraprofile
service-control --stop vmware-vapi-endpoint && service-control --start vmware-vapi-endpoint

After restarting the services on all affected vCenter Servers, retry the Workload Domain deletion operation.

For reference, see also:
"User session count is limited to 550. Existing session count is 550 for user" during SDDC Manager upgrade precheck or Lifecycle Manager

Powered by Wolken Software