Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1535582

Summary:	Require qemu > 2.10 and remove conditional -U support checks
Product:	[oVirt] vdsm	Reporter:	Ala Hino <ahino>
Component:	Core	Assignee:	Ala Hino <ahino>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Avihai <aefrat>
Severity:	high	Docs Contact:
Priority:	high
Version:	4.20.0	CC:	ahino, bugs, bzlotnik, ebenahar, nsoffer, ylavi
Target Milestone:	ovirt-4.2.4	Flags:	rule-engine: ovirt-4.2+ ylavi: exception+
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-06-26 08:34:21 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:	1567806
Bug Blocks:

Description Ala Hino 2018-01-17 16:26:44 UTC

Description of problem:
qemu-kvm-rhev-2.10.0 adds support for unsafe operation that we need when creating volumes (in order not to prepare and teardown the backing chain).

Requiring qemu-kvm-rhev-2.10.0 will enable us cleaning the code added in the following patch:
https://gerrit.ovirt.org/85875

All prepare work can be completely removed.

Comment 1 Allon Mureinik 2018-01-29 07:50:42 UTC

4.2.1 is currently planned before RHEL 7.5.
Let's not block on it.

Comment 2 Sandro Bonazzola 2018-04-18 11:15:25 UTC

We are still developing 4.2.3 and this bug is in modified with targeted 4.2.4.
Please double check target milestone and bug status.

Comment 3 Allon Mureinik 2018-04-24 08:23:37 UTC

Looking at vdsm.spec.in (current master, commit e56b5135b74b3996b9918891adfbdfca9a011495), in CentOS we're still using qemu 2.9, so this bz should definitely not be in MODIFIED.

Comment 4 Ala Hino 2018-04-24 08:32:38 UTC

Right ... this is the CentOS BZ: bug 1567806.

Comment 5 Avihai 2018-06-03 08:06:50 UTC

verified on 4.2.4

Comment 6 Sandro Bonazzola 2018-06-26 08:34:21 UTC

This bugzilla is included in oVirt 4.2.4 release, published on June 26th 2018.

Since the problem described in this bug report should be
resolved in oVirt 4.2.4 release, it has been closed with a resolution of CURRENT RELEASE.

If the solution does not work for you, please open a new bug report.