Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Description of problem:
there are two version of python after the upgrade, one is from el6

Version-Release number of selected component (if applicable):
preupgrade-assistant-1.0.2-11.el6.x86_64
preupgrade-assistant-contents-users-0.4.5-1.el6.noarch
redhat-upgrade-tool-0.7.6-1.el7.noarch


python-2.7.5-16.el7.x86_64
python-2.6.5-3.el6_0.2.i686
yum-3.4.3-115.el7.noarch

How reproducible:
tried once

Steps to Reproduce:
1. 
[root@pes-guest-89 ~]# yum
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.6.6 (r266:84292, Nov 21 2013, 10:39:36) 
[GCC 4.4.7 20120313 (Red Hat 4.4.7-4)]

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

[root@pes-guest-89 ~]# rpm -q python yum
python-2.7.5-16.el7.x86_64
python-2.6.5-3.el6_0.2.i686
yum-3.4.3-115.el7.noarch


Actual results:
yum does not work

Expected results:
one version of python


Additional info:

Can you attach /var/log/redhat_upgrade_tool.log and /var/log/upgrade.log?

Created attachment 876409 [details]
redhat_upgrade_tool.log

Created attachment 876410 [details]
upgrade.log

Marking python-2.6.5-3.el6_0.2.i686 as install for pygtksourceview-2.8.0-1.el6.x86_64


is the problem. There is no pygtksourceview in RHEL 7, so yum pulled in the i686 version from RHEL6 as a way to resolve the dependency for both 'python(abi) = 2.6' from pygtksourceview and 'python(abi) = 2.7' for RHEL 7 packages.

Fyi,
there are all not-upgraded i686 packages from rhel6 on my rhel6>rhel7 workstation
 
rpm -qa | grep i686 | grep el6
libpurple-2.7.9-27.el6.i686
python-libs-2.6.6-52.el6.i686
python-2.6.5-3.el6_0.2.i686
cyrus-sasl-lib-2.1.23-13.el6_3.1.i686
gdbm-1.8.0-36.el6.i686

rpm -q gdbm cyrus-sasl-lib python python-libs libpurple
gdbm-1.10-8.el7.x86_64
gdbm-1.8.0-36.el6.i686
cyrus-sasl-lib-2.1.26-17.el7.x86_64
cyrus-sasl-lib-2.1.23-13.el6_3.1.i686
python-2.7.5-16.el7.x86_64
python-2.6.5-3.el6_0.2.i686
python-libs-2.7.5-16.el7.x86_64
python-libs-2.6.6-52.el6.i686
libpurple-2.10.7-21.el7.x86_64
libpurple-2.7.9-27.el6.i686

This same problem is described more generally in bug 1062714, so marking this as a duplicate of that

*** This bug has been marked as a duplicate of bug 1062714 ***