Hi,
I am working with virtual container host (vCH) with vRA, everything looks fine but sometimes container provisioning takes lot of time which is not expected, I am not sure why it's happening. When i checked I found logs and got to know "vCH host keeps on performing data collection" at the backend and sometimes its successful sometimes it fails with the below error:
Host [https://x.x.x.x:2376] has been marked [DISABLED] after failure to perform data collection. Error message is: request failed, no additional details provided; Reason: {"message":"request failed, no additional details provided","stackTrace":["com.vmware.xenon.common.Operation.fail(Operation.java:1227)","com.vmware.xenon.common.http.netty.NettyHttpServiceClient.failExpiredRequests(NettyHttpServiceClient.java:834)","com.vmware.xenon.common.http.netty.NettyHttpServiceClient.handleMaintenance(NettyHttpServiceClient.java:781)","com.vmware.admiral.adapter.docker.service.RemoteApiDockerAdapterCommandExecutorImpl.handleMaintenance(RemoteApiDockerAdapterCommandExecutorImpl.java:515)","com.vmware.admiral.adapter.docker.service.AbstractDockerAdapterService.handleMaintenance(AbstractDockerAdapterService.java:102)","com.vmware.xenon.common.ServiceMaintenanceTracker.lambda$performServiceMaintenance$1(ServiceMaintenanceTracker.java:171)","com.vmware.xenon.common.ServiceHost.executeRunnableSafe(ServiceHost.java:5019)","com.vmware.xenon.common.ServiceHost.lambda$schedule$55(ServiceHost.java:5013)","java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)","java.util.concurrent.FutureTask.run(FutureTask.java:266)","java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)","java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)","java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)","java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)","java.lang.Thread.run(Thread.java:748)"],"statusCode":408,"documentKind":"com:vmware:xenon:common:ServiceErrorResponse","errorCode":0}
If anyone has worked on it and came across this error or any idea on why container provisioning takes time while provisioning with vCH please help.
