cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <>
Subject [jira] [Commented] (CLOUDSTACK-8530) KVM hosts without active agent connection are still "Up"
Date Tue, 02 Jun 2015 11:21:19 GMT


ASF GitHub Bot commented on CLOUDSTACK-8530:

Github user wilderrodrigues commented on the pull request:
    After running this on my KVM host:
    [root@kvm1 ~]# systemctl stop cloudstack-agent
    [root@kvm1 ~]# 
    The management server said:
    Then I started it agains:
    [root@kvm1 ~]# systemctl start cloudstack-agent
    [root@kvm1 ~]# systemctl status cloudstack-agent
    cloudstack-agent.service - SYSV: Cloud Agent
       Loaded: loaded (/etc/rc.d/init.d/cloudstack-agent)
       Active: active (running) since Tue 2015-06-02 07:20:10 EDT; 3s ago
      Process: 20054 ExecStop=/etc/rc.d/init.d/cloudstack-agent stop (code=exited, status=0/SUCCESS)
      Process: 20090 ExecStart=/etc/rc.d/init.d/cloudstack-agent start (code=exited, status=0/SUCCESS)
       CGroup: /system.slice/cloudstack-agent.service
               ├─20106 jsvc.exec -Xms256m -Xmx2048m -cp /usr/share/java/commons-daemon.jar:/usr/share/cloudstack-agent/lib/activation-1.1.jar:/usr/share/cloudstack-agent/lib/antisamy-1.4.3.jar:/usr/share/cloudstack-agent/lib/aopalliance-1.0.jar:/usr/share/cloudstack-agent/...
               └─20107 jsvc.exec -Xms256m -Xmx2048m -cp /usr/share/java/commons-daemon.jar:/usr/share/cloudstack-agent/lib/activation-1.1.jar:/usr/share/cloudstack-agent/lib/antisamy-1.4.3.jar:/usr/share/cloudstack-agent/lib/aopalliance-1.0.jar:/usr/share/cloudstack-agent/...
    Jun 02 07:20:10 kvm1 systemd[1]: Starting SYSV: Cloud Agent...
    Jun 02 07:20:10 kvm1 cloudstack-agent[20090]: Starting Cloud Agent:
    Jun 02 07:20:10 kvm1 systemd[1]: Started SYSV: Cloud Agent.
    [root@kvm1 ~]# 
    And on the UI:
    Thanks, Rohit!
    I will merge.

> 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