Bug 1489677 – [downstream clone - 4.1.7] If VM is down and 'run_on_vds' is still set, errors are reported in engine and server logs

Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.

Bug 1489677 - [downstream clone - 4.1.7] If VM is down and 'run_on_vds' is still set, errors are reported in engine and server logs

Summary:	[downstream clone - 4.1.7] If VM is down and 'run_on_vds' is still set, error...

Status:	CLOSED ERRATA

Aliases:	None

Product:	Red Hat Enterprise Virtualization Manager
Classification:	Red Hat
Component:	ovirt-engine (Show other bugs)
Sub Component:
Version:	4.1.2
Hardware:	Unspecified Linux

Priority	medium Severity high
Target Milestone:	ovirt-4.1.7
Target Release:	---
Assigned To:	Arik
QA Contact:	Nisim Simsolo
Docs Contact:

URL:
Whiteboard:
Keywords:	ZStream

Depends On:	1487728
Blocks:
	Show dependency tree / graph

Reported:	2017-09-08 02:20 EDT by rhev-integ
Modified:	2017-12-14 08:56 EST (History)
CC List:	13 users (show)

See Also:
Fixed In Version:
Doc Type:	If docs needed, set a value
Doc Text:
Story Points:	---
Clone Of:	1487728
Environment:
Last Closed:	2017-11-07 12:27:54 EST
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	Virt
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

External Trackers
Tracker	ID	Priority	Status	Summary	Last Updated
oVirt gerrit	81412	master	POST	core: update the required fields when vm disappears	2017-09-08 02:20 EDT
oVirt gerrit	81517	ovirt-engine-4.1	POST	core: update the required fields when vm disappears	2017-09-08 02:20 EDT
oVirt gerrit	81518	ovirt-engine-4.1	POST	core: prevent NPE when vm disappears from the host	2017-09-08 02:20 EDT
oVirt gerrit	82518	ovirt-engine-4.1	MERGED	core: clear migrating_to_vds when migration ends unexpectedly	2017-10-03 09:51 EDT
Red Hat Product Errata	RHEA-2017:3138	normal	SHIPPED_LIVE	Red Hat Virtualization Manager (ovirt-engine) 4.1.7	2017-11-07 17:22:33 EST

Groups: None (edit)

Description rhev-integ 2017-09-08 02:20:19 EDT

+++ 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)

Comment 5 rhev-integ 2017-09-08 02:20:41 EDT

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)

Comment 6 rhev-integ 2017-09-08 02:20:46 EDT

do we want also a 4.1 backport of https://gerrit.ovirt.org/#/c/81560/ ?

(Originally by michal.skrivanek)

Comment 10 errata-xmlrpc 2017-11-07 12:27:54 EST

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

Note You need to log in before you can comment on or make changes to this bug.