cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From koushik-das <>
Subject [GitHub] cloudstack issue #1640: CLOUDSTACK-9458: Fix HA bug when VMs are stopped on ...
Date Tue, 22 Nov 2016 05:23:14 GMT
Github user koushik-das commented on the issue:
    @marcaurele Thats correct. In case of shared/remote storage the same disk is used to spawn
a VM on another host once the VM is successfully fenced. If the fencer has successfully fenced
off a VM, it is assumed that the original VM is correctly stopped. Now if you are saying that
the original VM continues to run then that means that the specific fencer has bugs and needs
fixing. Note that there are different types of fencer available in cloudstack based on hypervisor
    @abhinandanprateek In the scenario you mentioned vmsync won't be able to mark VM as stopped
as the ping command is no longer running as the host is in alert/down state.

If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at or file a JIRA ticket
with INFRA.

View raw message