+++ This bug is a downstream clone. The original bug is: +++
+++ bug 1487728 +++
======================================================================
Description of problem:
If 'run_on_vds' in the vm_dynamic table in the RHV database contains a host id, but the VM is actually down, the engine will report the following;
- engine.log;
2017-08-31 07:43:23,615+05 INFO [org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer] (DefaultQuartzScheduler1) [] VM '6be6956f-b8b8-4a33-bb37-30334702b8b9'(cdvpgweb03) is running in db and not running on VDS 'e31634bf-d4a0-47e8-ba81-d49c280acaa3'(dch12bl13.cbec.gov.in)
2017-08-31 07:43:23,623+05 ERROR [org.ovirt.engine.core.utils.timer.SchedulerUtilQuartzImpl] (DefaultQuartzScheduler1) [] Failed to invoke scheduled method poll: null
- server.log;
2017-08-31 07:43:23,623+05 INFO [org.quartz.core.JobRunShell] (DefaultQuartzScheduler1) Job DEFAULT.org.ovirt.engine.core.vdsbroker.monitoring.PollVmStatsRefresher.poll#-9223372036854775759 threw a JobExecutionException: : org.quartz.JobExecutionException: failed to execute job
Version-Release number of selected component (if applicable):
RHV 4.1.2
RHVH 7.3 hosts
How reproducible:
100% if you force it to happen.
Steps to Reproduce:
1. Check VM is not running.
2. Set 'run_on_vds' in vm_dynamic to a valid host uuid.
3. Check engine and server logs.
Actual results:
Expected results:
Additional info:
(Originally by Gordon Watson)
They are not normal either way, but the host was responding, actually.
We should deal with the exception more gracefully, no matter how it happened (it may be restore from a backup)
(Originally by michal.skrivanek)
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHEA-2017:3138