Bug 1360990

Summary:	[z-stream clone - 4.0.4] VMs are not reported as non-responding even though qemu process does not responds.
Product:	Red Hat Enterprise Virtualization Manager	Reporter:	rhev-integ
Component:	vdsm	Assignee:	Francesco Romani <fromani>
Status:	CLOSED ERRATA	QA Contact:	sefi litmanovich <slitmano>
Severity:	high	Docs Contact:
Priority:	medium
Version:	3.6.7	CC:	bazulay, bgraveno, fromani, gklein, lsurette, mgoldboi, michal.skrivanek, mkalinin, rhodain, sbonazzo, srevivo, ycui, ykaul
Target Milestone:	ovirt-4.0.4	Keywords:	ZStream
Target Release:	4.0.4
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:	This update fixes a error in the monitoring code that caused the VDSM to incorrectly report that a QEMU process has recovered and is responsive after being unavailable for a short amount of time, while it was actually unresponsive.	Story Points:	---
Clone Of:	1357798	Environment:
Last Closed:	2016-09-28 22:17:25 UTC	Type:	---
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:	1357798
Bug Blocks:

Comment 1 sefi litmanovich 2016-09-05 08:53:20 UTC

Verified with rhevm-4.0.4-0.1.el7ev.noarch, host: vdsm-4.18.12-1.el7ev.x86_64.


Verified according to steps in description.
Result after kill -19 <qemu-pid> :
vdsClient is reporting the vm in state 'UP' with monitorResponse = -1. In engine the vm is reported as not responding which is the expected result.
Status isn't changed after several minutes, so no monitoring issues.
When resuming the process with kill -CONT <qemu-pid> monitorResponse = 0 and vm is back up in engine.

Comment 3 errata-xmlrpc 2016-09-28 22:17:25 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://rhn.redhat.com/errata/RHBA-2016-1950.html