Bug 1624846

Summary:	VDSM python3 compatibility
Product:	[oVirt] vdsm	Reporter:	Gal Zaidman <gzaidman>
Component:	Packaging.rpm	Assignee:	Marcin Sobczyk <msobczyk>
Status:	CLOSED NOTABUG	QA Contact:	Lukas Svaty <lsvaty>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	4.30.0	CC:	bugs, mperina, pkliczew
Target Milestone:	ovirt-4.4.0	Flags:	rule-engine: ovirt-4.4+
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:	2019-08-26 11:44:45 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	Infra	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	1460625, 1624790

Description Gal Zaidman 2018-09-03 12:32:54 UTC

With the need for python3.6 support for vdsm,
and considering the best practices for Python packaging,
https://fedoraproject.org/wiki/Packaging:Python#Byte_compiling
we must create separated packages for python-vdsm: python2-vdsm and python3-vdsm.

Having a package for python3.6 includes porting code to stop using dependencies that are python2-only or porting them ourselves if not possible some examples needed to be checked:
python-subprocess32,
ioprocess(https://bugzilla.redhat.com/show_bug.cgi?id=1257554),
python-pthreading,
sanlock-python,

Comment 1 Martin Perina 2018-09-03 15:30:57 UTC

This seems to me like a breaking backward compatibility change, which we don't want to do in 4.3. AFAIK in 4.3 we are only going to do code changes for parts which are broken in Python 3 but without altering Python 2 compatibility. And running VDSM on Python 3 without any issues is completely out of scope in 4.3. So moving to 4.4

Comment 2 Gal Zaidman 2019-08-26 11:44:45 UTC

VDSM is packaged for python3