Bug 1464002

Summary:	Consume libvirt fixes fox RHEL7.4 [depends on bug 1461303; bug 1470127 - fixed for 7.4.z]
Product:	[oVirt] vdsm	Reporter:	Tal Nisan <tnisan>
Component:	Packaging.rpm	Assignee:	Tal Nisan <tnisan>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Raz Tamir <ratamir>
Severity:	medium	Docs Contact:
Priority:	high
Version:	4.20.0	CC:	ahino, amureini, bugs, dyuan, ebenahar, eblake, hhan, jneedle, lmen, lmiksik, rbalakri, tnisan, xuzhang, yanqzhan
Target Milestone:	ovirt-4.1.7	Flags:	rule-engine: ovirt-4.1+ rule-engine: exception+
Target Release:	4.19.35
Hardware:	x86_64
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:	1461303	Environment:
Last Closed:	2017-11-13 12:24:40 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	Storage	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	1461303, 1504150
Bug Blocks:

Comment 1 Allon Mureinik 2017-07-03 07:06:53 UTC

The real fix for this problem is in libvirt, via bug 1461303. There are no code changes required from vdsm's side, so simply dnf updating libvirt to get libvirt-3.2.0-12.el7 once it's released will solve the problem.

RHV 4.1.4 will be released *before* this libvirt, so we can't require it there. On the other hand, the original bug occured on an unreleased libvirt build which no customer should ever encounter, so requiring it is a useful safety measure, but not a hard requirement.

Reducing priotiy/severity accordingly.

Comment 2 Allon Mureinik 2017-07-12 08:00:27 UTC

bug 1467826 is also a critical libvirt bug which should be delivered as a 0day errata by libvirt.

We should wait till that is released and require the right libvirt version that contains fixes for both bugs - bug 1461303 and bug 1467826.

Comment 3 Allon Mureinik 2017-08-07 12:31:24 UTC

There's nothing blocking here - customers who just yum update their environments will get these fixes. Having vdsm require them is an additional safety measure, but definitely not a must.

I prefer waiting for CentOS 7.4 instead of uglifying the spec file - pushing out.

Comment 4 Allon Mureinik 2017-10-01 10:07:28 UTC

The underlying issue is fixed by libvirt - this is just to track a failsagfe of requiring it.
Removing alarming keywords and the blocker flag.

Comment 5 Raz Tamir 2017-10-23 19:23:48 UTC

According to comment #4 - verifying