Bug 1304038 - docker-1.9 is unstable when used with openshift-3.1.
docker-1.9 is unstable when used with openshift-3.1.
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: docker (Show other bugs)
All Linux
urgent Severity urgent
: rc
: ---
Assigned To: Lokesh Mandvekar
Yoana Ruseva
: Extras, ZStream
Depends On:
  Show dependency treegraph
Reported: 2016-02-02 12:53 EST by Jeremy Eder
Modified: 2016-05-12 06:06 EDT (History)
6 users (show)

See Also:
Fixed In Version: docker-1.9.1-17.el7
Doc Type: Known Issue
Doc Text:
docker 1.9 is unstable when used with OpenShift 3.1 If docker 1.9 and atomic-openshift 3.1 / origin 1.1 are installed simultaneously, it causes stability issues. Customers should wait until atomic-openshift 3.2 / origin 1.2 are released before upgrading to docker 1.9. To ensure this, docker 1.9 has been packaged to conflict with atomic-openshift versions older than 3.2 and origin versions older than 1.2. OpenShift customers doing a "yum update" will get the docker-1.9 package *only if* they have atomic-openshift 3.2 / origin 1.2 or newer installed. Simultaneous installation of docker 1.9 with older versions of atomic-openshift or origin will not be allowed.
Story Points: ---
Clone Of:
Last Closed: 2016-03-31 19:23:50 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Jeremy Eder 2016-02-02 12:53:19 EST
Whole thread is here:

Original bug report and root cause is here:

We have 2 channels, that are released at different times.

1) RHEL Extras -- on the RHEL schedule and includes docker.  This is set to
release a new version of docker-1.9 in a few weeks.
2) OpenShift -- on their own schedule, but they rely on docker.
However...version 1.9 of docker has issues with the version of OpenShift,
which will come out after RHEL Extras ships docker-1.9.

We want to avoid openshift customers doing a 'yum update', and getting the
new version of docker ... ONLY IF ... they have openshift 3.1 installed.
We would like that to cause an error.

We want to somehow enforce that openshift customers avoid
docker-1.9+openshift-3.1.  We want customers to wait until openshift-3.2 in
order to use docker-1.9.
But we can't line up their release schedules.

We also want people without docker installed (or without openshift
installed at all), to be able to upgrade or install docker-1.9.

Jan Zelený from packaging-team suggests using 
Conflicts: openshift <= 3.1
Comment 2 Lokesh Mandvekar 2016-03-08 10:53:41 EST
Scott, as per your suggestions, I have in the upcoming rpm:

Conflicts: atomic-openshift < 3.2
Conflicts: origin < 1.2

PTAL and let me know if any changes.
Comment 4 Scott Dodson 2016-03-08 15:31:42 EST
(In reply to Lokesh Mandvekar from comment #2)
> Scott, as per your suggestions, I have in the upcoming rpm:
> Conflicts: atomic-openshift < 3.2
> Conflicts: origin < 1.2
> PTAL and let me know if any changes.

Looks good, thanks.
Comment 5 Jeremy Eder 2016-03-09 13:18:16 EST
Hey I guess it works:

# rpm -qa|egrep 'openshift|docker'|sort
root@dell-r620-01: ~/svt/openshift_scalability # yum update 
Loaded plugins: langpacks, product-id, search-disabled-repos, subscription-manager

Resolving Dependencies
--> Running transaction check
---> Package docker.x86_64 0:1.9.1-16.el7 will be updated
---> Package docker.x86_64 0:1.9.1-18.el7 will be an update
--> Processing Dependency: docker-forward-journald = 1.9.1-18.el7 for package: docker-1.9.1-18.el7.x86_64
---> Package docker-selinux.x86_64 0:1.9.1-16.el7 will be updated
---> Package docker-selinux.x86_64 0:1.9.1-18.el7 will be an update
--> Running transaction check
---> Package docker-forward-journald.x86_64 0:1.9.1-18.el7 will be installed
--> Processing Conflict: docker-1.9.1-18.el7.x86_64 conflicts atomic-openshift < 3.2
--> Finished Dependency Resolution
Error: docker conflicts with atomic-openshift-
 You could try using --skip-broken to work around the problem
 You could try running: rpm -Va --nofiles --nodigest
Comment 6 Scott Dodson 2016-03-09 13:27:48 EST
^^^ is the exact same thing someone installing OSE after this package ships will run into. I think this is undesirable and the wrong thing to do unless we have evidence that the problem manifests itself with default maxPods.
Comment 7 Luwen Su 2016-03-17 11:32:12 EDT
In spec file in docker-1.9.1-22.el7.x86_64
# rhbz#1304038
Conflicts: atomic-openshift < 3.2
Conflicts: origin < 1.2

Move to verified
Comment 9 errata-xmlrpc 2016-03-31 19:23:50 EDT
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, and where to find the updated
files, follow the link below.

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


Note You need to log in before you can comment on or make changes to this bug.