Bug 1872037
| Summary: | Unable to upgrade from OpenShift Container Platform 3.9 to a higher version due to python2-requests dependency | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Lark Gordon <lagordon> |
| Component: | Release | Assignee: | Luke Meyer <lmeyer> |
| Status: | CLOSED ERRATA | QA Contact: | liujia <jiajliu> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 3.11.0 | CC: | aos-bugs, eparis, jokerman, mbliss |
| Target Milestone: | --- | ||
| Target Release: | 3.11.z | ||
| 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: | 2020-09-16 07:46:50 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: | |||
This may be a dupe or closely related to https://bugzilla.redhat.com/show_bug.cgi?id=1859813 marking comment 0 as public, there's no sensitive information in there and it's helpful if things like this show up in search engines. It's the same bug (for customers instead of internals), although I'd modify the original statement somewhat. Upgrading to 3.10 ought to work since we did not ship python2-urllib3-1.24.3-1.el7 there. But trying to update to 3.11 will run into this problem. Copied from that bug: 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. The relevant things got tagged and put in our latest unsigned compose: http://download.eng.bos.redhat.com/rcm-guest/puddles/RHAOS/AtomicOpenShift/3.11/2020-08-30.1/ (or /building/) (We won't have signed until release.) I think it's worth testing independently from https://bugzilla.redhat.com/show_bug.cgi?id=1859813 - ensure that upgrades work. 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 |
Description of problem: When upgrading from OCP 3.9 to any higher version, dependency errors are displayed for python2-requests because it is no longer shipped in OCP. Version-Release number of selected component (if applicable): OCP 3.9 python2-requests-2.14.2-1.el7ost.noarch rhel-7-server-ose-3.9-rpms repo How reproducible: Very (will provide examples) Steps to Reproduce: 1. Install OCP 3.9 2. Attempt to upgrade to any newer version 3. Dependency error for python2-requests Actual results: Error: Package: python2-requests-2.14.2-1.el7ost.noarch (@rhel-7-server-ose-3.9-rpms) Requires: python2-urllib3 = 1.21.1 Removing: python2-urllib3-1.21.1-1.el7.noarch (@rhel-7-server-ose-3.10-rpms) python2-urllib3 = 1.21.1-1.el7 Updated By: python2-urllib3-1.24.3-1.el7.noarch (rhel-7-server-ose-3.11-rpms) python2-urllib3 = 1.24.3-1.el7 Available: python-urllib3-1.10.2-7.el7.noarch (rhel-7-server-rpms) python2-urllib3 = 1.10.2-7.el7 Available: python-urllib3-1.5-8.el7.noarch (rhel-7-server-rpms) ~python-urllib3 = 1.5-8.el7 Available: python-urllib3-1.10.2-1.el7_1.noarch (rhel-7-server-rpms) ~python-urllib3 = 1.10.2-1.el7_1 Available: python-urllib3-1.10.2-2.el7_1.noarch (rhel-7-server-rpms) ~python-urllib3 = 1.10.2-2.el7_1 Available: python-urllib3-1.10.2-3.el7.noarch (rhel-7-server-rpms) ~python-urllib3 = 1.10.2-3.el7 Available: python-urllib3-1.10.2-5.el7.noarch (rhel-7-server-rpms) ~python-urllib3 = 1.10.2-5.el7 You could try using --skip-broken to work around the problem Expected results: this package should be obsoleted or removed during upgrade. Additional info: the current suggested workaround is to remove this package from just the database only, however we're concerned this could cause issues on these systems later on.