[
https://issues.apache.org/jira/browse/CLOUDSTACK-8530?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14567885#comment-14567885
]
ASF GitHub Bot commented on CLOUDSTACK-8530:
--------------------------------------------
Github user mlsorensen commented on the pull request:
https://github.com/apache/cloudstack/pull/340#issuecomment-107684409
Looks fine to me.
On Mon, Jun 1, 2015 at 12:13 PM, Rohit Yadav <[email protected]>
wrote:
> pinging KVM and HA gurus to help review this @kishankavala
> <https://github.com/kishankavala> @wilderrodrigues
> <https://github.com/wilderrodrigues> @remibergsma
> <https://github.com/remibergsma> @mlsorensen
> <https://github.com/mlsorensen> @abhinandanprateek
> <https://github.com/abhinandanprateek> @devdeep
> <https://github.com/devdeep> and others
> thanks :)
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/apache/cloudstack/pull/340#issuecomment-107674771>.
>
> KVM hosts without active agent connection are still "Up"
> --------------------------------------------------------
>
> Key: CLOUDSTACK-8530
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8530
> 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
> 192.168.1.12 -j DROP (here 192.168.1.12 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
(v6.3.4#6332)
