Bug 1487728

Summary: If VM is down and 'run_on_vds' is still set, errors are reported in engine and server logs
Product: Red Hat Enterprise Virtualization Manager Reporter: Gordon Watson <gwatson>
Component: ovirt-engineAssignee: Arik <ahadas>
Status: CLOSED ERRATA QA Contact: Nisim Simsolo <nsimsolo>
Severity: high Docs Contact:
Priority: medium    
Version: 4.1.2CC: ahadas, gveitmic, gwatson, lsurette, michal.skrivanek, nsimsolo, rbalakri, Rhev-m-bugs, srevivo, tjelinek, ykaul, ylavi
Target Milestone: ovirt-4.2.0Keywords: ZStream
Target Release: ---Flags: lsvaty: testing_plan_complete-
Hardware: Unspecified   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: No Doc Update
Doc Text:
undefined
Story Points: ---
Clone Of:
: 1489677 (view as bug list) Environment:
Last Closed: 2018-05-15 17:43:37 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Virt RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1489677    

Description Gordon Watson 2017-09-01 18:27:33 UTC
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:

Comment 4 Michal Skrivanek 2017-09-04 13:28:25 UTC
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)

Comment 5 Michal Skrivanek 2017-09-08 06:17:56 UTC
do we want also a 4.1 backport of https://gerrit.ovirt.org/#/c/81560/ ?

Comment 7 Arik 2017-09-10 16:26:33 UTC
(In reply to Michal Skrivanek from comment #5)
> do we want also a 4.1 backport of https://gerrit.ovirt.org/#/c/81560/ ?

Yes

Comment 13 errata-xmlrpc 2018-05-15 17:43:37 UTC
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-2018:1488

Comment 14 Franta Kust 2019-05-16 13:06:57 UTC
BZ<2>Jira Resync

Comment 15 Daniel Gur 2019-08-28 13:13:45 UTC
sync2jira

Comment 16 Daniel Gur 2019-08-28 13:17:59 UTC
sync2jira