Bug 1638030

Summary: Need a regression job to test out Py3 support in Glusterfs code base
Product: [Community] GlusterFS Reporter: Shyamsundar <srangana>
Component: project-infrastructureAssignee: bugs <bugs>
Status: CLOSED UPSTREAM QA Contact:
Severity: low Docs Contact:
Priority: low    
Version: mainlineCC: bugs, gluster-infra, khiremat, mscherer
Target Milestone: ---Keywords: Triaged
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: 2020-03-12 12:54:08 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Shyamsundar 2018-10-10 13:55:55 UTC
Description of problem:

With the move towards Python3 we need a regression job (nightly initially) that exercises the tests on a platform that is Python3 by default.

Current regression on CentOS7 uses Python2 and to ensure we are working on both versions of Python we need a new job for Python3, and later as we move up CentOS versions or the default platform moves to Python3 we need to retain a Python2 regression job against an older platform till we support the same (this is just a note for later).

The tests can be filtered out to just run those that utilize Python code in the code base, but to start with let us get a full regression and once the pared down list is complete, we can reduce the scope of the job.

Comment 1 M. Scherer 2018-10-11 11:59:50 UTC
So, any version of python3 would do the trick, or do we have one in mind ?

Comment 2 Kaleb KEITHLEY 2018-10-11 12:27:35 UTC
survey of the platforms I build gluster for have:

rhel8: 3.6.6
fedora 30 (rawhide): 3.7
fedora 29: 3.7
fedora 28: 3.6.6
debian 10 (buster/sid): 3.6.7rc1
debian 9: 3.5.3
debian 8¹: 3.4.2
ubuntu 16.04 (xenial): 3.5.2
ubuntu 18.04 (bionic): 3.6.4+
ubuntu 18.10 (cosmic): 3.6.6
centos7 (w/ EPEL)²: 3.4.9 or 3.6.6

¹ We will not be building gluster-5 packages on debian 8.

² Information only. The packages in the CentOS Storage SIG will not use EPEL and will be python2.)

I'm not a python expert but I'd be inclined to be aggressive and use 3.7; 3.6.6 would be the lowest version I'd be interested in.

I have to wonder if rhel8 will update to 3.7 before it ships.

My 2¢

Comment 3 Nigel Babu 2018-10-15 02:19:02 UTC
Going to target this for Sprint 5.

Comment 5 Worker Ant 2020-03-12 12:54:08 UTC
This bug is moved to https://github.com/gluster/project-infrastructure/issues/35, and will be tracked there from now on. Visit GitHub issues URL for further details