Red Hat Bugzilla – Bug 1304038
docker-1.9 is unstable when used with openshift-3.1.
Last modified: 2016-05-12 06:06:58 EDT
Whole thread is here: http://post-office.corp.redhat.com/archives/packaging-team/2016-February/msg00001.html Original bug report and root cause is here: https://bugzilla.redhat.com/show_bug.cgi?id=1302408#c10 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
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.
(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.
Hey I guess it works: # rpm -qa|egrep 'openshift|docker'|sort atomic-openshift-3.1.1.911-1.git.0.14f4c71.el7.x86_64 atomic-openshift-clients-3.1.1.911-1.git.0.14f4c71.el7.x86_64 atomic-openshift-master-3.1.1.911-1.git.0.14f4c71.el7.x86_64 atomic-openshift-node-3.1.1.911-1.git.0.14f4c71.el7.x86_64 atomic-openshift-sdn-ovs-3.1.1.911-1.git.0.14f4c71.el7.x86_64 docker-1.9.1-16.el7.x86_64 docker-selinux-1.9.1-16.el7.x86_64 tuned-profiles-atomic-openshift-node-3.1.1.911-1.git.0.14f4c71.el7.x86_64 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-3.1.1.911-1.git.0.14f4c71.el7.x86_64 You could try using --skip-broken to work around the problem You could try running: rpm -Va --nofiles --nodigest
^^^ is the exact same thing someone installing OSE 3.1.1.6 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.
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
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. https://rhn.redhat.com/errata/RHBA-2016-0536.html