Bug 1728988

Summary:	release-5.7 glupy is not getting built during packaging.
Product:	[Community] GlusterFS	Reporter:	hari gowtham <hgowtham>
Component:	core	Assignee:	bugs <bugs>
Status:	CLOSED NEXTRELEASE	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	5	CC:	bugs
Target Milestone:	---
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-07-18 06:22:03 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:
Bug Depends On:
Bug Blocks:	1731014

Description hari gowtham 2019-07-11 07:17:52 UTC

Description of problem:
Glupy doesn't get built when packaged.
If python3 is installed with EPEL on centos, the configure.ac uses python3 but doesnt have python3 devel. so it skips building glupy.

Solution is to not install python3 by adding epel on centos or install python3 devel or use python2 over python3. 

We choose to use python2 to python3 as glupy was not python3 compatible. 

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

How reproducible:
install python3 on centos and try to package it.

Steps to Reproduce:
1.install python3 
2.do a ./autogen.sh and then ./configure
3../configure shows that glupy is not built.

Actual results:
glupy not built

Expected results:
glupy should be built

Additional info:
This is a corner case.

Comment 1 Worker Ant 2019-07-11 07:23:57 UTC

REVIEW: https://review.gluster.org/23028 (Configure changes to build with python2) posted (#1) for review on release-5 by hari gowtham

Comment 2 Worker Ant 2019-07-18 06:22:03 UTC

REVIEW: https://review.gluster.org/23028 (Configure changes to build with python2) merged (#2) on release-5 by hari gowtham