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

["edison su (JIRA)" <ji...@apache.org>]

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

edison su commented on CLOUDSTACK-5582:
---------------------------------------

Jakob, currently, there is no way to change the host state from "DIsconnected" to "Down" manually, unless you change DB.
"Disconnected" state is a temporary state, it should be changed to either "Alert" or "Down". If it's in "Alert" state, mgt server will start investigate the host's state by sending command(ping the host's ip address) to other hosts in the same cluster as the host, if the investigation failed, then host will remain in "Alert" state, or the state will be changed to "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.4.0
>
>         Attachments: kvmhost-down-up.rar, kvmhost-down-up.rar
>
>
> 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.2#6252)