<div dir="ltr"><div dir="ltr"><br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu, Jun 13, 2019 at 10:06 AM Kaleb Keithley <<a href="mailto:kkeithle@redhat.com" target="_blank">kkeithle@redhat.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div dir="ltr"><br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Wed, Jun 12, 2019 at 8:13 PM Deepshikha Khandelwal <<a href="mailto:dkhandel@redhat.com" target="_blank">dkhandel@redhat.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div dir="ltr"></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu, Jun 13, 2019 at 4:41 AM Kaleb Keithley <<a href="mailto:kkeithle@redhat.com" target="_blank">kkeithle@redhat.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div dir="ltr"><br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Wed, Jun 12, 2019 at 11:36 AM Kaleb Keithley <<a href="mailto:kkeithle@redhat.com" target="_blank">kkeithle@redhat.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div dir="ltr"><br></div><div dir="ltr"><div dir="ltr"><div dir="ltr">On Wed, Jun 12, 2019 at 10:43 AM Amar Tumballi Suryanarayan <<a href="mailto:atumball@redhat.com" target="_blank">atumball@redhat.com</a>> wrote:<br></div><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div dir="ltr"></div><div class="gmail_quote"><div><br></div><div>We recently noticed that in one of the package update on builder (ie, centos7.x machines), python3.6 got installed as a dependency. So, yes, it is possible to have python3 in centos7 now.</div></div></div></blockquote><div><br></div><div>EPEL updated from python34 to python36 recently, but C7 doesn't have python3 in the base. I don't think we've ever used EPEL packages for building.<br></div><div><br></div><div>And GlusterFS-5 isn't python3 ready.</div></div></div></div></div></blockquote><div><br></div><div><div>Correction: GlusterFS-5 is mostly or completely python3 ready.
FWIW, python33 is available on both RHEL7 and CentOS7 from the Software
Collection Library (SCL), and python34 and now python36 are available
from EPEL.</div><div><br></div><div>But packages built for the CentOS
Storage SIG have never used the SCL or EPEL (EPEL not allowed) and the
shebangs in the .py files are converted from /usr/bin/python3 to
/usr/bin/python2 during the rpmbuild %prep stage. All the python
dependencies for the packages remain the python2 flavors. AFAIK the
centos-regression machines ought to be building the same way.</div></div></div></div></blockquote><div><br></div><div>centos-regression machines have 'CentOS Linux release 7.6.1810 (Core)' and using python3.6. Looking at the tracebacks when compiling we confirmed that it is picking up python3.6 somehow. </div></div></div></blockquote><div><br></div><div>We need to figure out why? BTW, my CentOS 7 box is up to date and does not have any version of python3. I would have to use the SCL or EPEL to get it.<br></div><div><br></div><div>What changed on June 5th? Between <a href="https://build.gluster.org/job/centos7-regression/6309/consoleFull" target="_blank">https://build.gluster.org/job/centos7-regression/6309/consoleFull</a> and <a href="https://build.gluster.org/job/centos7-regression/6310/consoleFull" target="_blank">https://build.gluster.org/job/centos7-regression/6310/consoleFull</a>?</div></div></div></blockquote><div>Yes, you are right. OS got upgrade to newer version on 5th June. It has EPEL repo enabled for various other things.</div><div><br></div><div>Can we make changes in <a href="http://configure.ac">configure.ac</a> file (python version specific to the branches) rather than falling back to python2 for other branches too? </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div class="gmail_quote"><div><br></div><div>6309 was the last centos-regression with python2.7. 6310 and all subsequent centos-regressions have been built with python3.6.<br></div><div><br></div><div>Somebody added EPEL! Do we not have a record of the changes made and who made them?</div><div><br></div><div>And BTW, this affects more than just glusterfs-5, it's affecting all versions: glusterfs-4.1, glusterfs-5, glusterfs-6, and master.<br></div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div class="gmail_quote"><div>To resolve this issue either we can remove glupy from the release(which is dead anyways) or install glupy on the instances. <br></div></div></div></blockquote><div><br></div><div>Or you can resolve where python36 came from and undo the change that introduced it.<br></div><div><br></div><div>At the risk of being repetitious – reiterating what Niels said – it's highly unusual to remove features in a bug fix update.</div><div><br></div><div>It's also unusual to have switched to python3 on rhel7 like this. Was there any discussion of such a change? If there was I seem to have missed it.<br></div><div><br></div><div>I suggest figuring out where python3.6 on rhel7 came from. Fix that first. Removing glupy is a bandaid over a unrelated problem. Once the real problem is fixed then there can be a separate discussion about removing the glupy feature in glusterfs-5.</div><div><br></div><div>--</div><div><br></div><div>Kaleb<br></div></div></div>
</blockquote></div></div>