Github user koushik-das commented on the issue:
https://github.com/apache/cloudstack/pull/1640
@marcaurele Can you share the MS logs for this issue? We need to understand
the exact cause for restart of VM? When an agent/host is detected as 'Down', CS
tries to check if VMs on it are alive or not, if found alive nothing is done on
the VM.
Also if you think that the host got disconnected intermittently, then there
are ways to adjust the timeout in CS after which it will start investigating
the host status. Try adjusting the ping.timeout configuration parameter to see
if the issue is resolved.
The investigation to check if VM is alive or not is done for all VMs
irrespective of HA enabled or not. If a host is really down then it makes sense
to mark the VMs as stopped. Additionally for HA enabled VMs, after they are
successfully fenced off, attempt is made to restart them on other hosts in the
cluster.
---
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.
---
