You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "Sateesh Chodapuneedi (JIRA)" <ji...@apache.org> on 2014/07/11 12:21:06 UTC
[jira] [Commented] (CLOUDSTACK-7012) [Atomation] Vcenter Hang
during 4.4 automation runs
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7012?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14058615#comment-14058615 ]
Sateesh Chodapuneedi commented on CLOUDSTACK-7012:
--------------------------------------------------
ERROR [c.c.h.v.r.VmwareResource] (DirectAgentCronJob-500:ctx-756811b8) Unable to connect to vSphere server: 10.223.52.12
com.sun.xml.internal.ws.client.ClientTransportException: The server sent HTTP status code 503: Service Unavailable
at com.sun.xml.internal.ws.transport.http.client.HttpTransportPipe.checkStatusCode(HttpTransportPipe.java:296)
at com.sun.xml.internal.ws.transport.http.client.HttpTransportPipe.createResponsePacket(HttpTransportPipe.java:245)
at com.sun.xml.internal.ws.transport.http.client.HttpTransportPipe.process(HttpTransportPipe.java:203)
at com.sun.xml.internal.ws.transport.http.client.HttpTransportPipe.processRequest(HttpTransportPipe.java:122)
at com.sun.xml.internal.ws.transport.DeferredTransportPipe.processRequest(DeferredTransportPipe.java:123)
at com.sun.xml.internal.ws.api.pipe.Fiber.__doRun(Fiber.java:626)
at com.sun.xml.internal.ws.api.pipe.Fiber._doRun(Fiber.java:585)
at com.sun.xml.internal.ws.api.pipe.Fiber.doRun(Fiber.java:570)
at com.sun.xml.internal.ws.api.pipe.Fiber.runSync(Fiber.java:467)
at com.sun.xml.internal.ws.client.Stub.process(Stub.java:308)
at com.sun.xml.internal.ws.client.sei.SEIStub.doProcess(SEIStub.java:163)
at com.sun.xml.internal.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:98)
at com.sun.xml.internal.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:78)
at com.sun.xml.internal.ws.client.sei.SEIStub.invoke(SEIStub.java:135)
at com.sun.proxy.$Proxy399.retrieveServiceContent(Unknown Source)
at com.cloud.hypervisor.vmware.util.VmwareClient.connect(VmwareClient.java:144)
at com.cloud.hypervisor.vmware.resource.VmwareContextFactory.create(VmwareContextFactory.java:70)
at com.cloud.hypervisor.vmware.resource.VmwareContextFactory.getContext(VmwareContextFactory.java:88)
at com.cloud.hypervisor.vmware.resource.VmwareResource.getServiceContext(VmwareResource.java:4951)
at com.cloud.hypervisor.vmware.resource.VmwareResource.getServiceContext(VmwareResource.java:4927)
at com.cloud.hypervisor.vmware.resource.VmwareResource.gcAndKillHungWorkerVMs(VmwareResource.java:3888)
at com.cloud.hypervisor.vmware.resource.VmwareResource.getCurrentStatus(VmwareResource.java:3865)
at com.cloud.agent.manager.DirectAgentAttache$PingTask.runInContext(DirectAgentAttache.java:164)
at org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:49)
at org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56)
at org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:103)
at org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:53)
at org.apache.cloudstack.managed.context.ManagedContextRunnable.run(ManagedContextRunnable.java:46)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:304)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:178)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
> [Atomation] Vcenter Hang during 4.4 automation runs
> ---------------------------------------------------
>
> Key: CLOUDSTACK-7012
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7012
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the default.)
> Components: VMware
> Affects Versions: 4.4.0
> Environment: VCenter 5.0
> Exi 5.0
> Reporter: Rayees Namathponnan
> Assignee: Sateesh Chodapuneedi
> Priority: Critical
> Fix For: 4.4.0
>
> Attachments: catalina.rar
>
>
> This issue observed with 4.4 automation run with Vcenter 5.0, during BVT run VM deployment fail, if you try to connect VCenter from console gets below error
> Call "ServiceInstance.RetrieveContent" for object "ServiceInstance" on Server "10.223.52.12" failed.
> I was using same VCenter more 1.5 year, i never faced this issue earlier, then i tried to run automation with 4.2 and 4.3 build last week i didnt observe this issue, i think some of the changes in CS 4.4 causing VCenter to hang
> Observed below error in MS Log
> INFO [c.c.h.v.u.VmwareContext] (DirectAgentCronJob-455:ctx-71dce779) New VmwareContext object, current outstanding count: 451
> INFO [c.c.h.v.r.VmwareResource] (DirectAgentCronJob-455:ctx-71dce779) Scan hung worker VM to recycle
> INFO [c.c.h.v.u.VmwareContext] (DirectAgent-17:ctx-d197a13b 10.223.250.131) New VmwareContext object, current outstanding count: 452
--
This message was sent by Atlassian JIRA
(v6.2#6252)