Bug 1717876 - Gluster upstream regression tests are failing with centos 7.7
Summary: Gluster upstream regression tests are failing with centos 7.7
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: GlusterFS
Classification: Community
Component: tests
Version: mainline
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Kotresh HR
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-06-06 11:40 UTC by Kotresh HR
Modified: 2019-06-07 11:21 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-06-07 11:21:29 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:


Attachments (Terms of Use)


Links
System ID Priority Status Summary Last Updated
Gluster.org Gerrit 22833 None Abandoned tests: Use python2 for tests 2019-06-07 09:16:21 UTC

Description Kotresh HR 2019-06-06 11:40:44 UTC
Description of problem:
Gluster upstream regression tests are failing with centos 7.7 with python3
package delivered. The python test utility files are not python3 compatible.

Following are the test utility python files

/bugs/distribute/overlap.py
./bugs/nfs/socket-as-fifo.py
./features/ipctest.py
./utils/create-files.py
./utils/getfattr.py
./utils/gfid-access.py
./utils/libcxattr.py
./utils/pidof.py
./utils/setfattr.py
./utils/changelogparser.py

Each needs to be tested and made py2/py3 compatible

Version-Release number of selected component (if applicable):
mainline

How reproducible:
Always

Failures:

https://build.gluster.org/job/centos7-regression/6317/consoleFull &https://build.gluster.org/job/centos7-regression/6316/consoleFull

Comment 1 Worker Ant 2019-06-06 11:43:56 UTC
REVIEW: https://review.gluster.org/22833 (tests: Use python2 for tests) posted (#1) for review on master by Kotresh HR

Comment 2 Kotresh HR 2019-06-07 11:20:40 UTC
This patch fixed the issue and is merged

https://review.gluster.org/#/c/glusterfs/+/22829/


Note You need to log in before you can comment on or make changes to this bug.