[ https://issues.apache.org/jira/browse/CLOUDSTACK-3535?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13723512#comment-13723512 ]
Salvatore Sciacco edited comment on CLOUDSTACK-3535 at 7/30/13 7:41 AM: ------------------------------------------------------------------------ For shared storage using the CLVM corosync/cman is required, can't we use/require it for HA? It has quorum/fencing/etc... BTW in any case some workaround/hack to release the VM from the died host is required, some suggestion? was (Author: sas2000): For shared storage using the CLVM corosync/cman is required, can't we use/require it for HA? It has quorum/fencing/etc... > 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