Bug 1257554

Summary:	[CodeChange] - Build ioprocess for python3
Product:	[oVirt] ovirt-distribution	Reporter:	Yeela Kaplan <ykaplan>
Component:	ioprocess	Assignee:	Sandro Bonazzola <sbonazzo>
ioprocess sub component:	General	QA Contact:	Lucie Leistnerova <lleistne>
Status:	CLOSED CURRENTRELEASE	Docs Contact:
Severity:	high
Priority:	high	CC:	bugs, frolland, lleistne, lsvaty, mperina, nsoffer, pstehlik, tnisan
Version:	4.0.0	Keywords:	CodeChange
Target Milestone:	ovirt-4.4.0	Flags:	sbonazzo: ovirt-4.4? rule-engine: planning_ack+ amureini: devel_ack+ pstehlik: testing_ack+
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	No Doc Update
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-05-20 20:01:28 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	Integration	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	1241655
Bug Blocks:	1706987

Description Yeela Kaplan 2015-08-27 10:33:19 UTC

Description of problem:
Add an ioprocess package supporting python3

Comment 1 Yeela Kaplan 2015-08-27 10:36:36 UTC

Adding dependency,
waiting for python macros to get into fc21, el7.1.

Comment 2 Red Hat Bugzilla Rules Engine 2015-10-19 10:56:34 UTC

Target release should be placed once a package build is known to fix a issue. Since this bug is not modified, the target version has been reset. Please use target milestone to plan a fix for a oVirt release.

Comment 5 Martin Perina 2016-03-02 12:12:59 UTC

Moving to storage team as they should handle ioprocess now

Comment 6 Tal Nisan 2016-03-28 09:06:42 UTC

Nir, the patch is still relevant or should I remove it and move the bug back to new?

Comment 7 Mike McCune 2016-03-28 23:14:23 UTC

This bug was accidentally moved from POST to MODIFIED via an error in automation, please see mmccune with any questions

Comment 8 Allon Mureinik 2016-04-18 04:59:31 UTC

(In reply to Tal Nisan from comment #6)
> Nir, the patch is still relevant or should I remove it and move the bug back
> to new?
?

Comment 9 Nir Soffer 2016-04-18 06:22:42 UTC

(In reply to Allon Mureinik from comment #8)
> (In reply to Tal Nisan from comment #6)
> > Nir, the patch is still relevant or should I remove it and move the bug back
> > to new?
> ?

The patch looks relevant, but it is too risky for 4.0.

Comment 10 Allon Mureinik 2016-04-18 09:16:13 UTC

(In reply to Nir Soffer from comment #9)
> (In reply to Allon Mureinik from comment #8)
> > (In reply to Tal Nisan from comment #6)
> > > Nir, the patch is still relevant or should I remove it and move the bug back
> > > to new?
> > ?
> 
> The patch looks relevant, but it is too risky for 4.0.
Pushing out based on this assessment. Thanks.

Comment 11 Nir Soffer 2017-02-28 23:35:35 UTC

This will not be in 4.1, please schedule to 4.2.

Comment 12 Allon Mureinik 2017-07-16 09:16:57 UTC

This may be relevant in RHEL 8 where python 3 is the default. Util then, unless it's a very low hanging fruit, I frankly wouldn't bother.

Comment 13 Sandro Bonazzola 2019-01-28 09:40:55 UTC

This bug has not been marked as blocker for oVirt 4.3.0.
Since we are releasing it tomorrow, January 29th, this bug has been re-targeted to 4.3.1.

Comment 14 Sandro Bonazzola 2019-05-17 14:33:13 UTC

Done with https://gerrit.ovirt.org/#/c/99792/

Comment 15 Sandro Bonazzola 2020-05-20 20:01:28 UTC

This bugzilla is included in oVirt 4.4.0 release, published on May 20th 2020.

Since the problem described in this bug report should be
resolved in oVirt 4.4.0 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.