You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "Koushik Das (JIRA)" <ji...@apache.org> on 2013/12/20 04:58:07 UTC

[jira] [Commented] (CLOUDSTACK-5582) kvm - HA is not triggered when host is powered down since the host gets into "Disconnected" state.

    [ https://issues.apache.org/jira/browse/CLOUDSTACK-5582?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13853645#comment-13853645 ] 

Koushik Das commented on CLOUDSTACK-5582:
-----------------------------------------

HA gets triggered only when host is in 'Down' or 'Alert' state.

'Disconnected' state can also happen if the KVM agent is stopped but VMs are still running. So in case of a host power off it needs to be correctly determined as down.

> kvm - HA is not triggered when host is powered down since the host gets into "Disconnected" state. 
> ---------------------------------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-5582
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5582
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Management Server
>    Affects Versions: 4.3.0
>         Environment: Build from 4.3
>            Reporter: Sangeetha Hariharan
>            Assignee: edison su
>            Priority: Critical
>             Fix For: 4.3.0
>
>
> kvm - HA is not triggered when host is powered down since the host gets into "Disconnected" state.
> Advanced zone with  2 KVM (RHEL 6.3) hosts.
> Steps to reproduce the problem:
> Deploy few Vms in each of the hosts .
> Power down one of the hosts ( using IPMI).
> We see that the host gets into "Disconnected" state.
> All the Vms that are running in this host continue to be in "Up" state.
> This happens because of management server receiving a explicit shutdown request from the agent:
> 2013-12-19 21:06:37,262 DEBUG [c.c.a.m.AgentManagerImpl] (AgentManager-Handler-15:null) SeqA 2--1: Processing Seq 2--1:  { Cmd , MgmtId: -1, via: 2, Ver: v1, Flags: 111, [{"com.cloud.agent.api.ShutdownCommand":{"reason":"sig.kill","wait":0}}] }
> 2013-12-19 21:06:37,263 INFO  [c.c.a.m.AgentManagerImpl] (AgentManager-Handler-15:null) Host 2 has informed us that it is shutting down with reason sig.kill and detail null
> 2013-12-19 21:06:37,263 INFO  [c.c.a.m.AgentManagerImpl] (AgentTaskPool-1:ctx-a32ed8e2) Host 2 is disconnecting with event ShutdownRequested
> 2013-12-19 21:06:37,264 DEBUG [c.c.a.m.AgentManagerImpl] (AgentTaskPool-1:ctx-a32ed8e2) The next status of agent 2is Disconnected, current status is Up
> 2013-12-19 21:06:37,264 DEBUG [c.c.a.m.AgentManagerImpl] (AgentTaskPool-1:ctx-a32ed8e2) Deregistering link for 2 with state Disconnected
> 2013-12-19 21:06:37,264 DEBUG [c.c.a.m.AgentManagerImpl] (AgentTaskPool-1:ctx-a32ed8e2) Remove Agent : 2
> 2013-12-19 21:06:37,264 DEBUG [c.c.a.m.ConnectedAgentAttache] (AgentTaskPool-1:ctx-a32ed8e2) Processing Disconnect.



--
This message was sent by Atlassian JIRA
(v6.1.4#6159)