Accessing Availability view in the Cloud Director Portal automatically logs you out the current Cloud Director session
Article ID: 315030
Updated On:
Products
VMware Cloud Director
Issue/Introduction
Symptoms:
- When you access VMware Cloud Director Availability Portal from the Availability view in Cloud Director, you are automatically logged out of the current Cloud Director session.
- In /opt/vmware/h4/cloud/log/cloud.log on the Cloud Replication Management appliance, you see entries similar to:
2020-08-21 11:31:52.496 WARN - [8a97c34b-####-####-####-########e16] [health-check-3] c.v.r.health.HealthCheckingFactory : Resource is broken: VcloudSettings{apiVersion='31.0', queryPageSize=100} RestSettings{baseURI=https://vcd.corp.org:443/api, timeout=60000, maxConn=20, sniHostname='null', hostnameVerifier=null, clientCertificate=null, trustManager=com.vmware.rest.client.security.ShaTrustManager@9605fcda, authenticator=com.vmware.vcloud.client.auth.AccessTokenAuth@74471fcf}
com.vmware.vcloud.client.exception.VcloudAuthenticationException: null
at com.vmware.vcloud.client.VcloudClient.lambda$defaultErrorDeserializer$0(VcloudClient.java:212)
at com.vmware.rest.client.AbstractRestClient.convert(AbstractRestClient.java:219)
at com.vmware.vcloud.client.XmlRestClient.exchange(XmlRestClient.java:92)
at com.vmware.vcloud.client.XmlRestClient.exchange(XmlRestClient.java:68)
at com.vmware.vcloud.client.VcloudClient.exchange(VcloudClient.java:179)
at com.vmware.vcloud.client.VcloudClient.getResource(VcloudClient.java:930)
at com.vmware.h4.cloud.vcloud.VcloudHealthChecker.check(VcloudHealthChecker.java:48)
at com.vmware.h4.cloud.vcloud.VcloudHealthChecker.check(VcloudHealthChecker.java:22)
at com.vmware.resource.health.HealthCheckingFactory$4.run(HealthCheckingFactory.java:214)
at com.vmware.h4.common.mdc.MDCRunnableWrapper.run(MDCRunnableWrapper.java:30)
at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
at java.base/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:304)
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:834)
2020-08-21 11:31:52.497 DEBUG - [8a97c34b-####-####-####-########e16] [health-check-3] c.v.h4.cloud.vcloud.VcloudHealthChecker : Ignoring error for https://vcd.corp.org:443/api
2020-08-21 11:31:52.498 DEBUG - [8a97c34b-####-####-####-########e16] [health-check-3] c.v.h4.cloud.vcloud.VcloudHealthChecker : Disposing vCloud connection https://vcd.corp.org:443/api
com.vmware.vcloud.client.exception.VcloudAuthenticationException: null
at com.vmware.vcloud.client.VcloudClient.lambda$defaultErrorDeserializer$0(VcloudClient.java:212)
at com.vmware.rest.client.AbstractRestClient.convert(AbstractRestClient.java:219)
at com.vmware.vcloud.client.XmlRestClient.exchange(XmlRestClient.java:92)
at com.vmware.vcloud.client.XmlRestClient.exchange(XmlRestClient.java:68)
at com.vmware.vcloud.client.VcloudClient.exchange(VcloudClient.java:179)
at com.vmware.vcloud.client.VcloudClient.getResource(VcloudClient.java:930)
at com.vmware.h4.cloud.vcloud.VcloudHealthChecker.check(VcloudHealthChecker.java:48)
at com.vmware.h4.cloud.vcloud.VcloudHealthChecker.check(VcloudHealthChecker.java:22)
at com.vmware.resource.health.HealthCheckingFactory$4.run(HealthCheckingFactory.java:214)
at com.vmware.h4.common.mdc.MDCRunnableWrapper.run(MDCRunnableWrapper.java:30)
at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
at java.base/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:304)
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:834)
2020-08-21 11:31:52.497 DEBUG - [8a97c34b-####-####-####-########e16] [health-check-3] c.v.h4.cloud.vcloud.VcloudHealthChecker : Ignoring error for https://vcd.corp.org:443/api
2020-08-21 11:31:52.498 DEBUG - [8a97c34b-####-####-####-########e16] [health-check-3] c.v.h4.cloud.vcloud.VcloudHealthChecker : Disposing vCloud connection https://vcd.corp.org:443/api
Note: The preceding log excerpts are only examples. Date, time, and environmental variables may vary depending on your environment.
Environment
VMware Cloud Director Availability 4.x
Cause
This issue can occur when the primary Cloud Director cell in the VCD server group is experiencing issues that impact the Cloud Director Availability health check of Cloud Director.
Resolution
To resolve this issue, investigate and fix the issues impacting the primary cell of the connected Cloud Director instance.
Workaround:
To work around this issue, promote one of the standby Cloud Director cells to be the primary cell or re-configure the Cloud Director endpoint in Cloud Director Availability to point directly to a Cloud Director cell that is not experiencing any issues.
Workaround:
To work around this issue, promote one of the standby Cloud Director cells to be the primary cell or re-configure the Cloud Director endpoint in Cloud Director Availability to point directly to a Cloud Director cell that is not experiencing any issues.
- For more information on promoting a standy Cloud Director cell, see the Switch the Roles of the Primary and a Standby Cell in a Database High Availability Cluster section of the Cloud Director documentation.
- For more information on re-configuring the Cloud Director endpoint, see the Configure to Accept a Renewed VMware Cloud Director Endpoint or Certificate section of the Cloud Director Availability documentation.
Feedback
Yes
No
Powered by
