Bug 1859813

OpenShift doesn't ship python-requests-2.19, you're introducing these conflicts in some other repo, likely openstack repos as those are the only repos with python2-requests-2.19.1-4.el7ost.noarch
 please fix your repo configuration. If you want us to look into this any further please provide the output of `yum repolist -v` and `yum list installed`

I was wrong, that package is tagged into rhaos-3.11-rhel-7-image-build but I really don't know how it got there and if that's a repo that should be used for installation or not. Assigning to Release component as they control package tagging.

I think it got there by accident and failed to be removed via a different accident.

Should be resolved with http://download.eng.bos.redhat.com/rcm-guest/puddles/RHAOS/AtomicOpenShift-signed/3.11/2020-07-28.1/logs/changelog.log

(feel free to reopen as needed)

python2-urllib3-1.24.3-1.el7 was shipped to address https://bugzilla.redhat.com/show_bug.cgi?id=1700824 (the version shipping in RHEL7 never had the bug so hasn't been updated). That's where this started.

As you've discovered above, python2-urllib3-1.24.3-1.el7 is incompatible with the python2-requests that ships in RHEL. For images that use this RPM we pulled in dependencies that shipped with OpenStack. Initially we tagged in python-requests-2.19.1-4.el7ost then realized there were more and just configured to install all from the OpenStack repo.

We didn't realize python2-urllib3-1.24.3-1.el7 would interfere with openshift-ansible installs, though in retrospect it should have been obvious.

You could probably work around it by either installing an earlier version of python2-urllib3, excluding python2-urllib3-1.24.3-1.el7, or enabling openstack repos, but you shouldn't have to do that.

I think maybe we need to tag and ship all the related dependencies. And this might be needed for 4.y versions too, not certain.

Is https://bugzilla.redhat.com/show_bug.cgi?id=1872037 the same bug? package versions are different, it's unfortunate that comment 0 includes both public info that should be searchable and references to internal resources so i'll copy/paste the public bits into this comment for the sake of search engines finding this.

Scrubbed version of Comment 0 follows:

Description of problem:
=======================
While running a prerequisite for openshift-ansible 3.11.248-1 as it's failing with package dependency error. same package is present in both the repos python-requests-2.6.0-10.el7.noarch.rpm[1] and python2-requests-2.19.1-4.el7ost.noarch.rpm [2]. 


Version-Release number of selected component (if applicable):
=============================================================
Red Hat Enterprise Linux Server release 7.9 Beta (Maipo)
openshift-ansible-roles-3.11.248-1.git.0.fd212c7.el7.noarch


How reproducible:
=================
everytime

Steps to Reproduce:
===================
1. Enable repos and run prerequisite playbook

Actual results:
===============
 Error: Package: python2-requests-2.19.1-4.el7ost.noarch (downstream-rhel-7-server-ose-3.11-rpms)


Expected results:
=================
Deployment should be successful


Additional info:
================

    Error: Package: python2-requests-2.19.1-4.el7ost.noarch (downstream-rhel-7-server-ose-3.11-rpms)
               Requires: python-chardet >= 3.0.2
               Available: python-chardet-2.0.1-7.el7.noarch (downstream-rhel-7-server-rpms)
                   python-chardet = 2.0.1-7.el7
               Available: python-chardet-2.2.1-1.el7_1.noarch (downstream-rhel-7-server-rpms)
                   python-chardet = 2.2.1-1.el7_1
               Available: python-chardet-2.2.1-3.el7.noarch (downstream-RHEL-7-Server)
                   python-chardet = 2.2.1-3.el7

We found that RHEL [1] and OCP [2] repos contain the same package with different versions that are conflicting while installing OCP.

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (OpenShift Container Platform 3.11.286 bug fix and enhancement update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2020:3695