[jira] [Updated] (CLOUDSTACK-2140) Host is still marked as being in Up state when the host is shutdown (when there are no more hosts in the cluster)
[
https://issues.apache.org/jira/browse/CLOUDSTACK-2140?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sangeetha Hariharan updated CLOUDSTACK-2140:
Component/s: Management Server
Host is still marked as being in Up state when the host is shutdown (when
there are no more hosts in the cluster)
---
Key: CLOUDSTACK-2140
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2140
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: Management Server
Affects Versions: 4.2.0, 4.2.1
Environment: build from master
Reporter: Sangeetha Hariharan
Assignee: Koushik Das
Fix For: Future
Attachments: management-server.rar
Host is still marked as being in Up state when the host is shutdown (when
there are no more hosts in the cluster.
Set up:
Advanced zone.
3 hosts in a cluster ( in my case host id - 7 ,8 ,9 ).
I did not have any problems when host 8 and host 9 where shutdown.
When I tried to shutdown host 7 , I see the host still being in Up state ,
even after the management server detected that it is not able to connect with
this host.
Following exception seen in management server logs:
2013-04-22 14:48:18,350 DEBUG [xen.resource.XenServerConnectionPool]
(DirectAgent-350:null) localLogout has problem Failed to read server's
response: connect timed out
2013-04-22 14:48:18,350 WARN [xen.resource.CitrixResourceBase]
(DirectAgent-350:null) Unable to stop i-3-45-VM due to
com.cloud.utils.exception.CloudRuntimeException: Unable to reset master of
slave 10.223.59.4 to 10.223.59.2 due to org.apache.xmlrpc.XmlRpcException:
Failed to read server's response: connect timed out
at
com.cloud.hypervisor.xen.resource.XenServerConnectionPool.PoolEmergencyResetMaster(XenServerConnectionPool.java:443)
at
com.cloud.hypervisor.xen.resource.XenServerConnectionPool.connect(XenServerConnectionPool.java:661)
at
com.cloud.hypervisor.xen.resource.CitrixResourceBase.getConnection(CitrixResourceBase.java:5583)
at
com.cloud.hypervisor.xen.resource.CitrixResourceBase.execute(CitrixResourceBase.java:3728)
at
com.cloud.hypervisor.xen.resource.CitrixResourceBase.executeRequest(CitrixResourceBase.java:474)
at
com.cloud.hypervisor.xen.resource.XenServer56Resource.executeRequest(XenServer56Resource.java:73)
at
com.cloud.agent.manager.DirectAgentAttache$Task.run(DirectAgentAttache.java:186)
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
at java.util.concurrent.FutureTask.run(FutureTask.java:166)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:165)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:266)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
at java.lang.Thread.run(Thread.java:679)
2013-04-22 14:48:18,364 DEBUG [agent.manager.DirectAgentAttache]
(DirectAgent-350:null) Seq 9-72160431: Response Received:
2013-04-22 14:48:18,370 DEBUG [agent.transport.Request]
(DirectAgent-350:null) Seq 9-72160431: Processing: { Ans: , MgmtId:
7508777239729, via: 9, Ver: v1, Flags: 110,
[{StopAnswer:{result:false,details:Exception:
com.cloud.utils.exception.CloudRuntimeException\nMessage: Unable to reset
master of slave 10.223.59.4 to 10.223.59.2 due to
org.apache.xmlrpc.XmlRpcException: Failed to read server's response: connect
timed out\nStack: com.cloud.utils.exception.CloudRuntimeException: Unable to
reset master of slave 10.223.59.4 to 10.223.59.2 due to
org.apache.xmlrpc.XmlRpcException: Failed to read server's response: connect
timed out\n\tat
com.cloud.hypervisor.xen.resource.XenServerConnectionPool.PoolEmergencyResetMaster(XenServerConnectionPool.java:443)\n\tat
com.cloud.hypervisor.xen.resource.XenServerConnectionPool.connect(XenServerConnectionPool.java:661)\n\tat
com.cloud.hypervisor.xen.resource.CitrixResourceBase.getConnection(CitrixResourceBase.java:5583)\n\tat
com.cloud.hypervisor.xen.resource.CitrixResourceBase.execute(CitrixResourceBase.java:3728)\n\tat
com.cloud.hypervisor.xen.resource.CitrixResourceBase.executeRequest(CitrixResourceBase.java:474)\n\tat
com.cloud.hypervisor.xen.resource.XenServer56Resource.executeRequest(XenServer56Resource.java:73)\n\tat
[jira] [Updated] (CLOUDSTACK-2140) Host is still marked as being in Up state when the host is shutdown (when there are no more hosts in the cluster)
[
https://issues.apache.org/jira/browse/CLOUDSTACK-2140?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sangeetha Hariharan updated CLOUDSTACK-2140:
Priority: Critical (was: Major)
Bumping up the priority of this issue , since in case of basic zone we actually
see failures in programming the SG rules when Vms are started after both the
hosts in a cluster get rebooted at the same time.
Host is still marked as being in Up state when the host is shutdown (when
there are no more hosts in the cluster)
---
Key: CLOUDSTACK-2140
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2140
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: Management Server
Affects Versions: 4.2.0, 4.2.1
Environment: build from master
Reporter: Sangeetha Hariharan
Assignee: Koushik Das
Priority: Critical
Fix For: Future
Attachments: management-server.rar
Host is still marked as being in Up state when the host is shutdown (when
there are no more hosts in the cluster.
Set up:
Advanced zone.
3 hosts in a cluster ( in my case host id - 7 ,8 ,9 ).
I did not have any problems when host 8 and host 9 where shutdown.
When I tried to shutdown host 7 , I see the host still being in Up state ,
even after the management server detected that it is not able to connect with
this host.
Following exception seen in management server logs:
2013-04-22 14:48:18,350 DEBUG [xen.resource.XenServerConnectionPool]
(DirectAgent-350:null) localLogout has problem Failed to read server's
response: connect timed out
2013-04-22 14:48:18,350 WARN [xen.resource.CitrixResourceBase]
(DirectAgent-350:null) Unable to stop i-3-45-VM due to
com.cloud.utils.exception.CloudRuntimeException: Unable to reset master of
slave 10.223.59.4 to 10.223.59.2 due to org.apache.xmlrpc.XmlRpcException:
Failed to read server's response: connect timed out
at
com.cloud.hypervisor.xen.resource.XenServerConnectionPool.PoolEmergencyResetMaster(XenServerConnectionPool.java:443)
at
com.cloud.hypervisor.xen.resource.XenServerConnectionPool.connect(XenServerConnectionPool.java:661)
at
com.cloud.hypervisor.xen.resource.CitrixResourceBase.getConnection(CitrixResourceBase.java:5583)
at
com.cloud.hypervisor.xen.resource.CitrixResourceBase.execute(CitrixResourceBase.java:3728)
at
com.cloud.hypervisor.xen.resource.CitrixResourceBase.executeRequest(CitrixResourceBase.java:474)
at
com.cloud.hypervisor.xen.resource.XenServer56Resource.executeRequest(XenServer56Resource.java:73)
at
com.cloud.agent.manager.DirectAgentAttache$Task.run(DirectAgentAttache.java:186)
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
at java.util.concurrent.FutureTask.run(FutureTask.java:166)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:165)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:266)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
at java.lang.Thread.run(Thread.java:679)
2013-04-22 14:48:18,364 DEBUG [agent.manager.DirectAgentAttache]
(DirectAgent-350:null) Seq 9-72160431: Response Received:
2013-04-22 14:48:18,370 DEBUG [agent.transport.Request]
(DirectAgent-350:null) Seq 9-72160431: Processing: { Ans: , MgmtId:
7508777239729, via: 9, Ver: v1, Flags: 110,
[{StopAnswer:{result:false,details:Exception:
com.cloud.utils.exception.CloudRuntimeException\nMessage: Unable to reset
master of slave 10.223.59.4 to 10.223.59.2 due to
org.apache.xmlrpc.XmlRpcException: Failed to read server's response: connect
timed out\nStack: com.cloud.utils.exception.CloudRuntimeException: Unable to
reset master of slave 10.223.59.4 to 10.223.59.2 due to
org.apache.xmlrpc.XmlRpcException: Failed to read server's response: connect
timed out\n\tat
com.cloud.hypervisor.xen.resource.XenServerConnectionPool.PoolEmergencyResetMaster(XenServerConnectionPool.java:443)\n\tat
com.cloud.hypervisor.xen.resource.XenServerConnectionPool.connect(XenServerConnectionPool.java:661)\n\tat
com.cloud.hypervisor.xen.resource.CitrixResourceBase.getConnection(CitrixResourceBase.java:5583)\n\tat
com.cloud.hypervisor.xen.resource.CitrixResourceBase.execute(CitrixResourceBase.java:3728)\n\tat
[jira] [Updated] (CLOUDSTACK-2140) Host is still marked as being in Up state when the host is shutdown (when there are no more hosts in the cluster)
[
https://issues.apache.org/jira/browse/CLOUDSTACK-2140?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Abhinandan Prateek updated CLOUDSTACK-2140:
---
Fix Version/s: (was: 4.2.1)
Future
Host is still marked as being in Up state when the host is shutdown (when
there are no more hosts in the cluster)
---
Key: CLOUDSTACK-2140
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2140
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Affects Versions: 4.2.0, 4.2.1
Environment: build from master
Reporter: Sangeetha Hariharan
Assignee: Koushik Das
Fix For: Future
Attachments: management-server.rar
Host is still marked as being in Up state when the host is shutdown (when
there are no more hosts in the cluster.
Set up:
Advanced zone.
3 hosts in a cluster ( in my case host id - 7 ,8 ,9 ).
I did not have any problems when host 8 and host 9 where shutdown.
When I tried to shutdown host 7 , I see the host still being in Up state ,
even after the management server detected that it is not able to connect with
this host.
Following exception seen in management server logs:
2013-04-22 14:48:18,350 DEBUG [xen.resource.XenServerConnectionPool]
(DirectAgent-350:null) localLogout has problem Failed to read server's
response: connect timed out
2013-04-22 14:48:18,350 WARN [xen.resource.CitrixResourceBase]
(DirectAgent-350:null) Unable to stop i-3-45-VM due to
com.cloud.utils.exception.CloudRuntimeException: Unable to reset master of
slave 10.223.59.4 to 10.223.59.2 due to org.apache.xmlrpc.XmlRpcException:
Failed to read server's response: connect timed out
at
com.cloud.hypervisor.xen.resource.XenServerConnectionPool.PoolEmergencyResetMaster(XenServerConnectionPool.java:443)
at
com.cloud.hypervisor.xen.resource.XenServerConnectionPool.connect(XenServerConnectionPool.java:661)
at
com.cloud.hypervisor.xen.resource.CitrixResourceBase.getConnection(CitrixResourceBase.java:5583)
at
com.cloud.hypervisor.xen.resource.CitrixResourceBase.execute(CitrixResourceBase.java:3728)
at
com.cloud.hypervisor.xen.resource.CitrixResourceBase.executeRequest(CitrixResourceBase.java:474)
at
com.cloud.hypervisor.xen.resource.XenServer56Resource.executeRequest(XenServer56Resource.java:73)
at
com.cloud.agent.manager.DirectAgentAttache$Task.run(DirectAgentAttache.java:186)
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
at java.util.concurrent.FutureTask.run(FutureTask.java:166)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:165)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:266)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
at java.lang.Thread.run(Thread.java:679)
2013-04-22 14:48:18,364 DEBUG [agent.manager.DirectAgentAttache]
(DirectAgent-350:null) Seq 9-72160431: Response Received:
2013-04-22 14:48:18,370 DEBUG [agent.transport.Request]
(DirectAgent-350:null) Seq 9-72160431: Processing: { Ans: , MgmtId:
7508777239729, via: 9, Ver: v1, Flags: 110,
[{StopAnswer:{result:false,details:Exception:
com.cloud.utils.exception.CloudRuntimeException\nMessage: Unable to reset
master of slave 10.223.59.4 to 10.223.59.2 due to
org.apache.xmlrpc.XmlRpcException: Failed to read server's response: connect
timed out\nStack: com.cloud.utils.exception.CloudRuntimeException: Unable to
reset master of slave 10.223.59.4 to 10.223.59.2 due to
org.apache.xmlrpc.XmlRpcException: Failed to read server's response: connect
timed out\n\tat
com.cloud.hypervisor.xen.resource.XenServerConnectionPool.PoolEmergencyResetMaster(XenServerConnectionPool.java:443)\n\tat
com.cloud.hypervisor.xen.resource.XenServerConnectionPool.connect(XenServerConnectionPool.java:661)\n\tat
com.cloud.hypervisor.xen.resource.CitrixResourceBase.getConnection(CitrixResourceBase.java:5583)\n\tat
com.cloud.hypervisor.xen.resource.CitrixResourceBase.execute(CitrixResourceBase.java:3728)\n\tat
com.cloud.hypervisor.xen.resource.CitrixResourceBase.executeRequest(CitrixResourceBase.java:474)\n\tat
com.cloud.hypervisor.xen.resource.XenServer56Resource.executeRequest(XenServer56Resource.java:73)\n\tat
[jira] [Updated] (CLOUDSTACK-2140) Host is still marked as being in Up state when the host is shutdown (when there are no more hosts in the cluster)
[
https://issues.apache.org/jira/browse/CLOUDSTACK-2140?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Abhinandan Prateek updated CLOUDSTACK-2140:
---
Fix Version/s: (was: 4.2.0)
4.2.1
Host is still marked as being in Up state when the host is shutdown (when
there are no more hosts in the cluster)
---
Key: CLOUDSTACK-2140
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2140
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Affects Versions: 4.2.0, 4.2.1
Environment: build from master
Reporter: Sangeetha Hariharan
Assignee: Koushik Das
Fix For: 4.2.1
Attachments: management-server.rar
Host is still marked as being in Up state when the host is shutdown (when
there are no more hosts in the cluster.
Set up:
Advanced zone.
3 hosts in a cluster ( in my case host id - 7 ,8 ,9 ).
I did not have any problems when host 8 and host 9 where shutdown.
When I tried to shutdown host 7 , I see the host still being in Up state ,
even after the management server detected that it is not able to connect with
this host.
Following exception seen in management server logs:
2013-04-22 14:48:18,350 DEBUG [xen.resource.XenServerConnectionPool]
(DirectAgent-350:null) localLogout has problem Failed to read server's
response: connect timed out
2013-04-22 14:48:18,350 WARN [xen.resource.CitrixResourceBase]
(DirectAgent-350:null) Unable to stop i-3-45-VM due to
com.cloud.utils.exception.CloudRuntimeException: Unable to reset master of
slave 10.223.59.4 to 10.223.59.2 due to org.apache.xmlrpc.XmlRpcException:
Failed to read server's response: connect timed out
at
com.cloud.hypervisor.xen.resource.XenServerConnectionPool.PoolEmergencyResetMaster(XenServerConnectionPool.java:443)
at
com.cloud.hypervisor.xen.resource.XenServerConnectionPool.connect(XenServerConnectionPool.java:661)
at
com.cloud.hypervisor.xen.resource.CitrixResourceBase.getConnection(CitrixResourceBase.java:5583)
at
com.cloud.hypervisor.xen.resource.CitrixResourceBase.execute(CitrixResourceBase.java:3728)
at
com.cloud.hypervisor.xen.resource.CitrixResourceBase.executeRequest(CitrixResourceBase.java:474)
at
com.cloud.hypervisor.xen.resource.XenServer56Resource.executeRequest(XenServer56Resource.java:73)
at
com.cloud.agent.manager.DirectAgentAttache$Task.run(DirectAgentAttache.java:186)
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
at java.util.concurrent.FutureTask.run(FutureTask.java:166)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:165)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:266)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
at java.lang.Thread.run(Thread.java:679)
2013-04-22 14:48:18,364 DEBUG [agent.manager.DirectAgentAttache]
(DirectAgent-350:null) Seq 9-72160431: Response Received:
2013-04-22 14:48:18,370 DEBUG [agent.transport.Request]
(DirectAgent-350:null) Seq 9-72160431: Processing: { Ans: , MgmtId:
7508777239729, via: 9, Ver: v1, Flags: 110,
[{StopAnswer:{result:false,details:Exception:
com.cloud.utils.exception.CloudRuntimeException\nMessage: Unable to reset
master of slave 10.223.59.4 to 10.223.59.2 due to
org.apache.xmlrpc.XmlRpcException: Failed to read server's response: connect
timed out\nStack: com.cloud.utils.exception.CloudRuntimeException: Unable to
reset master of slave 10.223.59.4 to 10.223.59.2 due to
org.apache.xmlrpc.XmlRpcException: Failed to read server's response: connect
timed out\n\tat
com.cloud.hypervisor.xen.resource.XenServerConnectionPool.PoolEmergencyResetMaster(XenServerConnectionPool.java:443)\n\tat
com.cloud.hypervisor.xen.resource.XenServerConnectionPool.connect(XenServerConnectionPool.java:661)\n\tat
com.cloud.hypervisor.xen.resource.CitrixResourceBase.getConnection(CitrixResourceBase.java:5583)\n\tat
com.cloud.hypervisor.xen.resource.CitrixResourceBase.execute(CitrixResourceBase.java:3728)\n\tat
com.cloud.hypervisor.xen.resource.CitrixResourceBase.executeRequest(CitrixResourceBase.java:474)\n\tat
com.cloud.hypervisor.xen.resource.XenServer56Resource.executeRequest(XenServer56Resource.java:73)\n\tat
[jira] [Updated] (CLOUDSTACK-2140) Host is still marked as being in Up state when the host is shutdown (when there are no more hosts in the cluster)
[
https://issues.apache.org/jira/browse/CLOUDSTACK-2140?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sangeetha Hariharan updated CLOUDSTACK-2140:
Affects Version/s: 4.2.1
Host is still marked as being in Up state when the host is shutdown (when
there are no more hosts in the cluster)
---
Key: CLOUDSTACK-2140
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2140
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Affects Versions: 4.2.0, 4.2.1
Environment: build from master
Reporter: Sangeetha Hariharan
Assignee: Koushik Das
Fix For: 4.2.0
Attachments: management-server.rar
Host is still marked as being in Up state when the host is shutdown (when
there are no more hosts in the cluster.
Set up:
Advanced zone.
3 hosts in a cluster ( in my case host id - 7 ,8 ,9 ).
I did not have any problems when host 8 and host 9 where shutdown.
When I tried to shutdown host 7 , I see the host still being in Up state ,
even after the management server detected that it is not able to connect with
this host.
Following exception seen in management server logs:
2013-04-22 14:48:18,350 DEBUG [xen.resource.XenServerConnectionPool]
(DirectAgent-350:null) localLogout has problem Failed to read server's
response: connect timed out
2013-04-22 14:48:18,350 WARN [xen.resource.CitrixResourceBase]
(DirectAgent-350:null) Unable to stop i-3-45-VM due to
com.cloud.utils.exception.CloudRuntimeException: Unable to reset master of
slave 10.223.59.4 to 10.223.59.2 due to org.apache.xmlrpc.XmlRpcException:
Failed to read server's response: connect timed out
at
com.cloud.hypervisor.xen.resource.XenServerConnectionPool.PoolEmergencyResetMaster(XenServerConnectionPool.java:443)
at
com.cloud.hypervisor.xen.resource.XenServerConnectionPool.connect(XenServerConnectionPool.java:661)
at
com.cloud.hypervisor.xen.resource.CitrixResourceBase.getConnection(CitrixResourceBase.java:5583)
at
com.cloud.hypervisor.xen.resource.CitrixResourceBase.execute(CitrixResourceBase.java:3728)
at
com.cloud.hypervisor.xen.resource.CitrixResourceBase.executeRequest(CitrixResourceBase.java:474)
at
com.cloud.hypervisor.xen.resource.XenServer56Resource.executeRequest(XenServer56Resource.java:73)
at
com.cloud.agent.manager.DirectAgentAttache$Task.run(DirectAgentAttache.java:186)
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
at java.util.concurrent.FutureTask.run(FutureTask.java:166)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:165)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:266)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
at java.lang.Thread.run(Thread.java:679)
2013-04-22 14:48:18,364 DEBUG [agent.manager.DirectAgentAttache]
(DirectAgent-350:null) Seq 9-72160431: Response Received:
2013-04-22 14:48:18,370 DEBUG [agent.transport.Request]
(DirectAgent-350:null) Seq 9-72160431: Processing: { Ans: , MgmtId:
7508777239729, via: 9, Ver: v1, Flags: 110,
[{StopAnswer:{result:false,details:Exception:
com.cloud.utils.exception.CloudRuntimeException\nMessage: Unable to reset
master of slave 10.223.59.4 to 10.223.59.2 due to
org.apache.xmlrpc.XmlRpcException: Failed to read server's response: connect
timed out\nStack: com.cloud.utils.exception.CloudRuntimeException: Unable to
reset master of slave 10.223.59.4 to 10.223.59.2 due to
org.apache.xmlrpc.XmlRpcException: Failed to read server's response: connect
timed out\n\tat
com.cloud.hypervisor.xen.resource.XenServerConnectionPool.PoolEmergencyResetMaster(XenServerConnectionPool.java:443)\n\tat
com.cloud.hypervisor.xen.resource.XenServerConnectionPool.connect(XenServerConnectionPool.java:661)\n\tat
com.cloud.hypervisor.xen.resource.CitrixResourceBase.getConnection(CitrixResourceBase.java:5583)\n\tat
com.cloud.hypervisor.xen.resource.CitrixResourceBase.execute(CitrixResourceBase.java:3728)\n\tat
com.cloud.hypervisor.xen.resource.CitrixResourceBase.executeRequest(CitrixResourceBase.java:474)\n\tat
com.cloud.hypervisor.xen.resource.XenServer56Resource.executeRequest(XenServer56Resource.java:73)\n\tat
[jira] [Updated] (CLOUDSTACK-2140) Host is still marked as being in Up state when the host is shutdown (when there are no more hosts in the cluster)
[
https://issues.apache.org/jira/browse/CLOUDSTACK-2140?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sangeetha Hariharan updated CLOUDSTACK-2140:
Attachment: management-server.rar
Host is still marked as being in Up state when the host is shutdown (when
there are no more hosts in the cluster)
---
Key: CLOUDSTACK-2140
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2140
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Affects Versions: 4.2.0
Environment: build from master
Reporter: Sangeetha Hariharan
Fix For: 4.2.0
Attachments: management-server.rar
Host is still marked as being in Up state when the host is shutdown (when
there are no more hosts in the cluster.
Set up:
Advanced zone.
3 hosts in a cluster ( in my case host id - 7 ,8 ,9 ).
I did not have any problems when host 8 and host 9 where shutdown.
When I tried to shutdown host 7 , I see the host still being in Up state ,
even after the management server detected that it is not able to connect with
this host.
Following exception seen in management server logs:
2013-04-22 14:48:18,350 DEBUG [xen.resource.XenServerConnectionPool]
(DirectAgent-350:null) localLogout has problem Failed to read server's
response: connect timed out
2013-04-22 14:48:18,350 WARN [xen.resource.CitrixResourceBase]
(DirectAgent-350:null) Unable to stop i-3-45-VM due to
com.cloud.utils.exception.CloudRuntimeException: Unable to reset master of
slave 10.223.59.4 to 10.223.59.2 due to org.apache.xmlrpc.XmlRpcException:
Failed to read server's response: connect timed out
at
com.cloud.hypervisor.xen.resource.XenServerConnectionPool.PoolEmergencyResetMaster(XenServerConnectionPool.java:443)
at
com.cloud.hypervisor.xen.resource.XenServerConnectionPool.connect(XenServerConnectionPool.java:661)
at
com.cloud.hypervisor.xen.resource.CitrixResourceBase.getConnection(CitrixResourceBase.java:5583)
at
com.cloud.hypervisor.xen.resource.CitrixResourceBase.execute(CitrixResourceBase.java:3728)
at
com.cloud.hypervisor.xen.resource.CitrixResourceBase.executeRequest(CitrixResourceBase.java:474)
at
com.cloud.hypervisor.xen.resource.XenServer56Resource.executeRequest(XenServer56Resource.java:73)
at
com.cloud.agent.manager.DirectAgentAttache$Task.run(DirectAgentAttache.java:186)
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
at java.util.concurrent.FutureTask.run(FutureTask.java:166)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:165)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:266)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
at java.lang.Thread.run(Thread.java:679)
2013-04-22 14:48:18,364 DEBUG [agent.manager.DirectAgentAttache]
(DirectAgent-350:null) Seq 9-72160431: Response Received:
2013-04-22 14:48:18,370 DEBUG [agent.transport.Request]
(DirectAgent-350:null) Seq 9-72160431: Processing: { Ans: , MgmtId:
7508777239729, via: 9, Ver: v1, Flags: 110,
[{StopAnswer:{result:false,details:Exception:
com.cloud.utils.exception.CloudRuntimeException\nMessage: Unable to reset
master of slave 10.223.59.4 to 10.223.59.2 due to
org.apache.xmlrpc.XmlRpcException: Failed to read server's response: connect
timed out\nStack: com.cloud.utils.exception.CloudRuntimeException: Unable to
reset master of slave 10.223.59.4 to 10.223.59.2 due to
org.apache.xmlrpc.XmlRpcException: Failed to read server's response: connect
timed out\n\tat
com.cloud.hypervisor.xen.resource.XenServerConnectionPool.PoolEmergencyResetMaster(XenServerConnectionPool.java:443)\n\tat
com.cloud.hypervisor.xen.resource.XenServerConnectionPool.connect(XenServerConnectionPool.java:661)\n\tat
com.cloud.hypervisor.xen.resource.CitrixResourceBase.getConnection(CitrixResourceBase.java:5583)\n\tat
com.cloud.hypervisor.xen.resource.CitrixResourceBase.execute(CitrixResourceBase.java:3728)\n\tat
com.cloud.hypervisor.xen.resource.CitrixResourceBase.executeRequest(CitrixResourceBase.java:474)\n\tat
com.cloud.hypervisor.xen.resource.XenServer56Resource.executeRequest(XenServer56Resource.java:73)\n\tat
com.cloud.agent.manager.DirectAgentAttache$Task.run(DirectAgentAttache.java:186)\n\tat
