Github user koushik-das commented on the issue:
https://github.com/apache/cloudstack/pull/1640
Please use a proper ACS release for reporting bugs. In your case you may
have to do some additional cherry-picks.
"Schedule restart" does multiple tasks. There is a method by this name in
code, the name may not be the most appropriate but it does the following. So
don't get confused with the name
1. Tries to find out if the VM is alive or not
2. If it is not able to determine conclusively if VM is alive, then it
tries to fence off VM
3. After successful fencing, HA enabled VMs are restarted on another host,
non-HA VMs are marked as Stopped
So as you see non-HA VMs are simply stopped when the host is determined as
down and not restarted. It makes sense to mark them as stopped so that
subsequent operations can be performed on the VMs, for e.g. selective VMs may
be explicitly started on another host. If a host is down then power sync won't
happen for that host and VM states on that host won't get updated.
---
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.
---
