[
https://issues.apache.org/jira/browse/CLOUDSTACK-3535?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13723504#comment-13723504
]
Paul Angus commented on CLOUDSTACK-3535:
----------------------------------------
I think we can all agree there isn't an easy fix staring us in the face, so we
need to think in broader terms.If we need to have the KVM CloudStack agent
start thinking in terms of pools/clusters with some quorum logic then thats
whats needed.
HA is a major component. 'Allowing' manual intervention is not good enough just
because the CloudStack infrastructure doesn't already include a handy tool we
can utilise.
> 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
> Assignee: 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
