cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From marcaurele <>
Subject [GitHub] cloudstack issue #1640: CLOUDSTACK-9458: Fix HA bug when VMs are stopped on ...
Date Tue, 23 Aug 2016 07:03:04 GMT
Github user marcaurele commented on the issue:
    > If the MS is not able to determine the state of the VM, it tries fencing off the
VM (using the various fencers available). If VM cannot be fenced off successfully, the state
of the VM is left unchanged. 
    Apparently I found a way where the VMs are successfully fenced off even though they should
    What is the reason to try fencing off VMs when the MS is not able to determine its state?
I cannot see a good reason so far but you seem to think there is at least one. Can you explain
    @jburwell It does not cover my case exactly as it's a timing issue. I'll keep a note to
find a way to create a scenario.

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