Github user marcaurele commented on the issue:
https://github.com/apache/cloudstack/pull/1640
To get back to your previous comment @koushik-das on the broken scenario:
what happen if the host is not reachable and the VMs are using a remote
storage. With the fencing operation marking the VM as stopped, does it mean
that the same remote disk volume is used if the VM is spawned on another host
(while the other one still running on the first host)?
@abhinandanprateek if the reason to fence off the VM is to clean up
resources, IMO this should be the job of the VM sync, on the ping
command/startup command. In case a host is lost, the capacity of the cluster
should reflect the lose of that host and the stat capacity should calculate its
value based on the hosts that are Up only. When a host comes back (possibly
with some VMs still running), the startup command should sync the VM states and
the capacity of the cluster/zone should be updated.
In short, cleaning up resources that are not "reachable" anymore should not
be needed and should not be taken into account when calculating the actual
capacity of the cluster/zone.
---
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 infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
