Bug 1487728 - If VM is down and 'run_on_vds' is still set, errors are reported in engine and server logs
Summary: If VM is down and 'run_on_vds' is still set, errors are reported in engine an...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: ovirt-engine
Version: 4.1.2
Hardware: Unspecified
OS: Linux
medium
high
Target Milestone: ovirt-4.2.0
: ---
Assignee: Arik
QA Contact: Nisim Simsolo
URL:
Whiteboard:
Depends On:
Blocks: 1489677
TreeView+ depends on / blocked
 
Reported: 2017-09-01 18:27 UTC by Gordon Watson
Modified: 2021-05-01 16:17 UTC (History)
12 users (show)

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
undefined
Clone Of:
: 1489677 (view as bug list)
Environment:
Last Closed: 2018-05-15 17:43:37 UTC
oVirt Team: Virt
Target Upstream Version:
Embargoed:
lsvaty: testing_plan_complete-

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2018:1488 0 None None None 2018-05-15 17:45:35 UTC
oVirt gerrit 81412 0 master MERGED core: update the required fields when vm disappears 2020-08-04 03:55:49 UTC
oVirt gerrit 81517 0 ovirt-engine-4.1 MERGED core: update the required fields when vm disappears 2020-08-04 03:55:49 UTC
oVirt gerrit 81518 0 ovirt-engine-4.1 MERGED core: prevent NPE when vm disappears from the host 2020-08-04 03:55:49 UTC
oVirt gerrit 81560 0 None MERGED core: clear migrating_to_vds when migration ends unexpectedly 2020-08-04 03:55:49 UTC

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
Note You need to log in before you can comment on or make changes to this bug.