Bug 1676855

Summary:	Package the provider driver for python2/3 compatibility
Product:	[oVirt] ovirt-provider-ovn	Reporter:	Miguel Duarte Barroso <mduarted>
Component:	driver	Assignee:	Miguel Duarte Barroso <mduarted>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Michael Burman <mburman>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	1.2.22	CC:	bugs, danken, dholler, mburman, royoung
Target Milestone:	ovirt-4.4.0	Flags:	sbonazzo: ovirt-4.4?
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-05-20 20:02:18 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	Network	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Miguel Duarte Barroso 2019-02-13 12:01:59 UTC

Require the correct python2/3 packages according to the python version being used and OS and make python3 syntax code changes if needed

Comment 1 Sandro Bonazzola 2019-08-01 07:12:09 UTC

This seems to be fixed in 1.2.25 for 4.3.6, should this be re-targeted? Can be verified on Fedora for python 3.

Comment 2 Miguel Duarte Barroso 2019-08-01 10:19:07 UTC

It is fixed in 1.2.25.

I pass the question to Dominik - is this worth a re-target ?

Comment 3 Dominik Holler 2019-08-01 10:33:02 UTC

(In reply to Sandro Bonazzola from comment #1)
> Can be verified on Fedora for python 3.

Any idea who will do the verification?

Comment 4 Dominik Holler 2019-08-01 10:34:14 UTC

unintentionally targeted to ovirt-4.3.6, we should know how to verify before

Comment 6 Michael Burman 2019-10-24 09:59:40 UTC

Verified on rhv-4.4.0 with
rhel 8.1 hosts
ovirt-provider-ovn-driver-1.2.27-1.el8ev.noarch
ovirt-provider-ovn-1.2.26-1.el7ev.noarch
rhv-openvswitch-ovn-host-2.11-6.el8ev.noarch
ovn2.11-host-2.11.0-16.el8fdp.x86_64

Comment 7 Sandro Bonazzola 2020-05-20 20:02:18 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.