You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "Likitha Shetty (JIRA)" <ji...@apache.org> on 2014/09/05 06:34:26 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=14122404#comment-14122404 ]
Likitha Shetty commented on CLOUDSTACK-7012:
--------------------------------------------
>From the logs, I see that the issue where CCP is ‘Unable to connect to the vCenter’ occurred on 01-08-2014, 23-08-2014 and 24-08-2014 . On these days the connection was lost for around 2 minutes only. Hence vCenter operations that were attempted by CCP in this 2 minute time frame failed.
But I don’t see any irrecoverable or lasting impact on CCP for e.g. hosts going into Alert state and not recovering. Rayees, Is there any such impact on the BVT run?
On 23-08-2014, connection to vCenter was lost between 19:43:47 and 19:46:01. And on 24-08-2014 it was lost between 19:46:04 and 19:48:24.
{noformat}
2014-08-23 19:43:47,842 ERROR [c.c.h.v.r.VmwareResource] (DirectAgent-279:ctx-0eadeff3 10.223.250.130, job-48, cmd: GetStorageStatsCommand) Unable to connect to vSphere server: 10.223.52.12
com.sun.xml.internal.ws.client.ClientTransportException: HTTP transport error: java.net.ConnectException: Connection refused
2014-08-23 19:46:01,835 ERROR [c.c.h.v.r.VmwareResource] (DirectAgent-489:ctx-39941295 10.223.250.130, job-54, cmd: GetHostStatsCommand) Unable to connect to vSphere server: 10.223.52.12
com.sun.xml.internal.ws.client.ClientTransportException: HTTP transport error: java.net.ConnectException: Connection timed out
{noformat}
{noformat}
2014-08-24 19:46:04,793 ERROR [c.c.h.v.r.VmwareResource] (DirectAgentCronJob-65:ctx-1ebb04bc) Unable to connect to vSphere server: 10.223.52.12
com.sun.xml.internal.ws.client.ClientTransportException: HTTP transport error: java.net.ConnectException: Connection refused
2014-08-24 19:48:24,320 ERROR [c.c.h.v.r.VmwareResource] (DirectAgent-373:ctx-a75e99a3 10.223.250.130, job-9797, cmd: GetHostStatsCommand) Unable to connect to vSphere server: 10.223.52.12
com.sun.xml.internal.ws.client.ClientTransportException: HTTP transport error: java.net.ConnectException: Connection timed out
{noformat}
I couldn't find anything relevant in the vCenter logs for the corresponding timelines. By any chance are you aware of any scheduled task on vCenter that could result in a downtime?
> [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, 4.5.0
> Environment: VCenter 5.0
> Exi 5.0
> Reporter: Rayees Namathponnan
> Assignee: Likitha Shetty
> Priority: Blocker
> Fix For: 4.5.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.3.4#6332)