Github user koushik-das commented on the pull request:
https://github.com/apache/cloudstack/pull/829#issuecomment-141418450
@DaanHoogland As per logs attached in bug VR reboot happened due to
out-of-band movement from one host to another and not due to power report
missing.
Host 19 reports VM is missing.
2015-09-15 09:37:06,508 DEBUG [c.c.v.VirtualMachinePowerStateSyncImpl]
(DirectAgentCronJob-253:ctx-c4f59216) Detected missing VM. host: 19, vm id:
342, power state: PowerReportMissing, last state update: 1442302506000
Host 20 reports that VM is running. Now since VM moved out-of-band from
host 19 to 20, VR got rebooted as per the previous code.
2015-09-15 09:37:07,809 DEBUG [c.c.v.VirtualMachinePowerStateSyncImpl]
(DirectAgentCronJob-254:ctx-757ec6a9) VM state report. host: 20, vm id: 342,
power state: PowerOn
2015-09-15 09:37:07,845 INFO [c.c.n.r.VirtualNetworkApplianceManagerImpl]
(DirectAgentCronJob-254:ctx-757ec6a9) Schedule a router reboot task as router
342 is powered-on out-of-band. we need to reboot to refresh network rules
There was a commit to remove the VR reboot. So now in this scenario VR
should continue to run. So the bug should no longer be there.
@resmo Before we talk about any fix, can you verify if the issue is still
happening on latest master?
---
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.
---
