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

ASF GitHub Bot commented on CLOUDSTACK-8530:
--------------------------------------------

Github user bhaisaab commented on the pull request:

    https://github.com/apache/cloudstack/pull/340#issuecomment-107943645
  
    @wilderrodrigues thanks, but the test you did is perhaps not enough as it 
cleanly shutsdown the agent. In my test, I did these things:
    - kill -9 the agent to see what happens
    - add firewall rule to block mgmt server traffic to the kvm host, using 
something like: iptables -A INPUT -s 192.168.1.12 -j DROP
    - using a cluster of three nodes, add the firewall rules to see how it 
behaves when neighbours report it is Up/Down and host is not reachable


> 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)

Reply via email to