[
https://issues.apache.org/jira/browse/CLOUDSTACK-3535?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13723464#comment-13723464
]
Abhinandan Prateek commented on CLOUDSTACK-3535:
------------------------------------------------
When a host goes offline, the cloudstack has several investigator to figure out
if the host if only disconnected from MS or if it is off the network. In case
of Xenserver you go thru pool master or any connected host in the pool.
In case of KVM there is no concept of pool, so if a host goes offline there is
no way to determine if it is disconnected from MS or if it is off the network.
Any HA action initiated when a KVM host is not offline could result in problems.
If we know that a KVM host has gone offline and is not on network we can allow
it to be manually disconnected.
> No HA actions are performed when a KVM host goes offline
> --------------------------------------------------------
>
> Key: CLOUDSTACK-3535
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3535
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Hypervisor Controller, KVM, Management Server
> Affects Versions: 4.1.0, 4.1.1, 4.2.0
> Environment: KVM (CentOS 6.3) with CloudStack 4.1
> Reporter: Paul Angus
> Priority: Blocker
> Attachments: management-server.log.Agent
>
>
> If a KVM host 'goes down', CloudStack does not perform HA for instances which
> are marked as HA enabled on that host (including system VMs)
> CloudStack does not show the host as disconnected.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
