1203143 - Replace system python with 2.7 in centos6-build image

Status: RESOLVED INCOMPLETE

(Release Engineering :: General, defect)

Description

[Dustin J. Mitchell [:dustin] (he/him)]

Typically this is a dangerous thing to do on CentOS because lots of the CentOS innards -- including yum -- depend on Python-2.6.  However, once we've don all of the yum installs, we won't run any of those innards, so it's probably safe to just make the default Python 2.7.

This does kill yum, though:

[root@taskcluster-worker ~]# for x in  /usr/bin/*2.7; do y=$(basename $x 2.7); y=$(basename $y -); echo $y; cp $x /usr/bin/$y; done
easy_install
peep
pip
python
[root@taskcluster-worker ~]# python
Python 2.7.10 (default, Sep  3 2015, 12:44:06) 
[GCC 4.4.7 20120313 (Red Hat 4.4.7-16)] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> 
[root@taskcluster-worker ~]# yum repolist
There was a problem importing one of the Python modules
required to run yum. The error leading to this problem was:

   No module named yum

Please install a package which provides this module, or
verify that the module is installed correctly.

It's possible that the above module doesn't match the
current version of Python, which is:
2.7.10 (default, Sep  3 2015, 12:44:06) 
[GCC 4.4.7 20120313 (Red Hat 4.4.7-16)]

If you cannot solve this problem yourself, please go to 
the yum faq at:
  http://yum.baseurl.org/wiki/Faq
  

and developers may find it useful to be able to 'yum install' various things while playing with the image.  But hacking /usr/bin/yum to run /usr/bin/python2.6 seems to fix that problem.

Is this insane?