cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <>
Subject [jira] [Commented] (CLOUDSTACK-8530) KVM hosts without active agent connection are still "Up"
Date Tue, 02 Jun 2015 12:57:17 GMT


ASF subversion and git services commented on CLOUDSTACK-8530:

Commit d55d45348c978294d0ba28de146160769d87ba81 in cloudstack's branch refs/heads/4.5 from
[;h=d55d453 ]

CLOUDSTACK-8530: KVM hosts without active agents should be in Disconnected state

KVM hosts which are actuall up, but if their agents are shutdown should be put
in disconnected state. This would avoid getting the VMs HA'd and other commands
such as deploying a VM will exclude that host and save us from errors.

The improvement is that, we first try to contact the KVM host itself. If it fails
we assume that it's disconnected, and then ask its KVM neighbours if they can
check its status. If all of the KVM neighbours tell us that it's Down and we're
unable to reach the KVM host, then the host is possibly down. In case any of the
KVM neighbours tell us that it's Up but we're unable to reach the KVM host then
we can be sure that the agent is offline but the host is running.

Signed-off-by: Rohit Yadav <>

This closes #340

> KVM hosts without active agent connection are still "Up"
> --------------------------------------------------------
>                 Key: CLOUDSTACK-8530
>                 URL:
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: KVM
>            Reporter: Rohit Yadav
>            Assignee: Rohit Yadav
>             Fix For: 4.6.0, 4.5.2
> KVM hosts without active agent connection are still "Up". In case a KVM host get uncleanly
disconnected from the mgmt server, for example due to a firewall rule or physical nic unplugging
the neighbour KVM hosts might investigate and report that the KVM host is in Up state but
since mgmt server is not connected to the agent (on that host), all further commands such
as VM migrations, VM deployments etc fail. 
> The best fix would be to have the investigator check the KVM host itself and if it's
unable to contact return the state as disconnected, this way no HA for VMs will be triggered.
> To reproduce the issue:
> 1. On a KVM host, drop packets from mgmt server host IP: iptables -A INPUT -s
-j DROP (here is the mgmt server IP)
> 2. After Investigator kicks in neighbours report that it's Up, now deploy a VM on this
host it fails.

This message was sent by Atlassian JIRA

View raw message