Bug 1324130 - Latest RHEL repo packages conflict with latest 3.1.* RPMs due to Docker dependencies
Summary: Latest RHEL repo packages conflict with latest 3.1.* RPMs due to Docker depen...
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: docker
Version: 7.2
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: rc
: ---
Assignee: Daniel Walsh
QA Contact: atomic-bugs@redhat.com
Yoana Ruseva
URL:
Whiteboard:
Depends On:
Blocks: 1323238
TreeView+ depends on / blocked
 
Reported: 2016-04-05 15:07 UTC by Boris Kurktchiev
Modified: 2019-10-10 11:47 UTC (History)
9 users (show)

Fixed In Version: docker-1.9.1-29.el7
Doc Type: Release Note
Doc Text:
Introduced conflict between docker 1.9 and atomic-openshift 3.1 / origin 1.1 has been removed Previously, due to stability issues between docker 1.9 and atomic-openshift 3.1 / origin 1.1, docker 1.9 has been packaged to conflict with atomic-openshift versions older than 3.2 and origin versions older than 1.2. As a consequence, running "yum update" on an OpenShift Enterprise 3.1 system failed due to that introduced conflict. This bug has been fixed, and running "yum update" now does not cause conflicts, successfully solves the dependencies and installs docker 1.9.
Clone Of:
Environment:
Last Closed: 2016-05-05 18:14:08 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Boris Kurktchiev 2016-04-05 15:07:30 UTC 
Description of problem:
yum upgrade
--> Finished Dependency Resolution
Error: docker conflicts with atomic-openshift-3.1.1.6-4.git.32.adf8ec9.el7aos.x86_64
 You could try using --skip-broken to work around the problem
 You could try running: rpm -Va --nofiles --nodigest

Version-Release number of selected component (if applicable):
3.1.1.6

How reproducible:
Try running yum upgrade on a RHEL 7 box

Steps to Reproduce:
1. yum upgrade
2. see dependency break due to docker 1.9.1

Actual results:
Dependency failing

Expected results:
Clean Upgrade

Additional info:
Basically as it sits right now upgrading a host system is problematic as any automated process we have in place has the potential to break our OSE installation.
Comment 1 Brenton Leanhardt 2016-04-05 15:44:15 UTC 
You should be able to 'yum install docker-1.8.2' preinstall to workaround this problem.  We're getting a build through testing as soon as we can to address this properly.

*** This bug has been marked as a duplicate of bug 1323057 ***
Comment 2 Scott Dodson 2016-04-05 15:52:30 UTC 
I think this bug is unique. Regardless of what we do in the installer or in atomic-openshift packaging a 'yum upgrade' after installing 3.1.1.6 will still fail without adding '--skip-broken' or upgrading to 3.2.

Reopening this.
Comment 4 Boris Kurktchiev 2016-04-06 16:04:22 UTC 
As Scott mentioned in comment 2, right now I am unable to run yum upgrade on any of my OSE 3.1.* systems as they all fail due to the docker conflict. This has only been remedied by modifying our system upgrade procedure temporarily as to allow the rest of the system to upgrade on the necessary cycle.
Comment 5 Lokesh Mandvekar 2016-04-18 17:42:48 UTC 
Conflicts will be removed in an upcoming build.
Comment 6 Eric Jones 2016-05-03 15:50:44 UTC 
@Lokesh,

An upcoming build of what? And is it out yet?
Comment 7 Lokesh Mandvekar 2016-05-03 15:57:05 UTC 
(In reply to Eric Jones from comment #6)
> @Lokesh,
> 
> An upcoming build of what? And is it out yet?

docker rpm, will be out in the next RHEL extras update.
Comment 13 Lokesh Mandvekar 2016-05-05 18:14:08 UTC 
The removal of conflicts between openshift and docker will be release noted.

CLOSED NEXTRELEASE as per QE.
Note You need to log in before you can comment on or make changes to this bug.