Red Hat Bugzilla – Bug 1323238
OSE 3.1 RPM should require docker >= 1.8.2 and < 1.9
Last modified: 2016-04-20 10:35:41 EDT
Docker-1.9.1-25 which was released yesterday has Conflicts: atomic-openshift < 3.2. While adding this won't prevent errors if a user runs 'yum upgrade' or if they've already installed docker-1.9.1 it will make it easier for greenfield installs.
(In reply to Scott Dodson from comment #0) > Docker-1.9.1-25 which was released yesterday has Conflicts: atomic-openshift > < 3.2. While adding this won't prevent errors if a user runs 'yum upgrade' > or if they've already installed docker-1.9.1 it will make it easier for > greenfield installs. Run "yum update" on ose-3.1 node, docker-1.9.1-25 will be updated, will get the following error: # yum update Loaded plugins: product-id, search-disabled-repos, subscription-manager This system is not registered to Red Hat Subscription Management. You can use subscription-manager to register. Resolving Dependencies --> Running transaction check ---> Package docker.x86_64 0:1.8.2-10.el7 will be updated ---> Package docker.x86_64 0:1.9.1-25.el7 will be an update --> Processing Dependency: docker-forward-journald = 1.9.1-25.el7 for package: docker-1.9.1-25.el7.x86_64 --> Running transaction check ---> Package docker-forward-journald.x86_64 0:1.9.1-25.el7 will be installed --> Processing Conflict: docker-1.9.1-25.el7.x86_64 conflicts atomic-openshift < 3.2 --> 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 I think docker rpm conflicts setting already prevent docker updated, it is enough. While because new openshift rpm is adding more restricted limit for docker version, continue this bug's verification with atomic-openshift-node-3.1.1.6-5.git.35.0742c54.el7aos.x86_64, and PASS. # rpm -qR atomic-openshift-node <--snip--> docker-io >= 1.8.2 docker-io < 1.9 <--snip--> # yum update Loaded plugins: product-id, search-disabled-repos, subscription-manager This system is not registered to Red Hat Subscription Management. You can use subscription-manager to register. Resolving Dependencies --> Running transaction check ---> Package docker.x86_64 0:1.8.2-10.el7 will be updated --> Processing Dependency: docker-io < 1.9 for package: atomic-openshift-node-3.1.1.6-5.git.35.0742c54.el7aos.x86_64 ---> Package docker.x86_64 0:1.9.1-25.el7 will be an update --> Processing Dependency: docker-forward-journald = 1.9.1-25.el7 for package: docker-1.9.1-25.el7.x86_64 --> Running transaction check ---> Package docker.x86_64 0:1.8.2-10.el7 will be updated --> Processing Dependency: docker-io < 1.9 for package: atomic-openshift-node-3.1.1.6-5.git.35.0742c54.el7aos.x86_64 ---> Package docker-forward-journald.x86_64 0:1.9.1-25.el7 will be installed --> Processing Conflict: docker-1.9.1-25.el7.x86_64 conflicts atomic-openshift < 3.2 --> Finished Dependency Resolution Error: Package: atomic-openshift-node-3.1.1.6-5.git.35.0742c54.el7aos.x86_64 (@ose-devel) Requires: docker-io < 1.9 Removing: docker-1.8.2-10.el7.x86_64 (@rhel-7-extra) docker-io = 1.8.2-10.el7 Updated By: docker-1.9.1-25.el7.x86_64 (rhel-7-extra) docker-io = 1.9.1-25.el7 Available: docker-1.2.0-1.8.el7.x86_64 (rhel-7-extra) docker-io Available: docker-1.3.2-4.el7.x86_64 (rhel-7-extra) docker-io = 1.3.2 Available: docker-1.4.1-37.el7.x86_64 (rhel-7-extra) docker-io = 1.4.1-37.el7 Available: docker-1.5.0-27.el7.x86_64 (rhel-7-extra) docker-io = 1.5.0-27 Available: docker-1.5.0-28.el7.x86_64 (rhel-7-extra) docker-io = 1.5.0-28 Available: docker-1.6.0-11.el7.x86_64 (rhel-7-extra) docker-io = 1.6.0-11 Available: docker-1.6.2-14.el7.x86_64 (rhel-7-extra) docker-io = 1.6.2-14 Available: docker-1.7.1-108.el7.x86_64 (rhel-7-extra) docker-io = 1.7.1-108.el7 Available: docker-1.7.1-115.el7.x86_64 (rhel-7-extra) docker-io = 1.7.1-115.el7 Available: docker-1.8.2-7.el7.x86_64 (rhel-7-extra) docker-io = 1.8.2-7.el7 Available: docker-1.8.2-8.el7.x86_64 (rhel-7-extra) docker-io = 1.8.2-8.el7 Available: docker-0.11.1-19.el7.x86_64 (rhel-7-extra) Not found Available: docker-0.11.1-22.el7.x86_64 (rhel-7-extra) Not found Available: docker-1.1.2-13.el7.x86_64 (rhel-7-extra) Not found Error: docker conflicts with atomic-openshift-3.1.1.6-5.git.35.0742c54.el7aos.x86_64 You could try using --skip-broken to work around the problem You could try running: rpm -Va --nofiles --nodigest
@Scott, after re-reading your initial report, your fix are trying to allow user to run "yum update" without error? If that, according to comment 2, I should assign this bug back, pls help confirm my verification in comment 2 are right.
Jianlin, Sorry, what I meant was that this bug will only fix situations where you install atomic-openshift-node on a host without docker pre-installed. There's nothing in the RPM we can do to prevent problems when you either a) install docker-1.9 first or b) after installing successfully run 'yum upgrade' Those two issues must be fixed via the installer, we're addressing those in this bug https://bugzilla.redhat.com/show_bug.cgi?id=1320695 Steps to Reproduce: 1. Provision host with access to OSE 3.1 channels and rhel extras 2. yum install atomic-openshift-node Actual results: Dependency errors. --> Running transaction check ---> Package atomic-openshift-clients.x86_64 0:3.1.1.6-4.git.32.adf8ec9.el7aos will be installed --> Processing Conflict: docker-1.9.1-25.el7.x86_64 conflicts atomic-openshift < 3.2 --> Processing Conflict: docker-1.9.1-25.el7.x86_64 conflicts atomic-openshift < 3.2 --> 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 Expected results: Successful installation. --> Running transaction check ---> Package atomic-openshift.x86_64 0:3.2.0.11-1.git.0.6696e29.el7 will be installed --> Processing Dependency: atomic-openshift-clients = 3.2.0.11-1.git.0.6696e29.el7 for package: atomic-openshift-3.2.0.11-1.git.0.6696e29.el7.x86_64 ---> Package docker.x86_64 0:1.9.1-25.el7 will be installed ---> Package tuned-profiles-atomic-openshift-node.x86_64 0:3.2.0.11-1.git.0.6696e29.el7 will be installed --> Running transaction check ---> Package atomic-openshift-clients.x86_64 0:3.2.0.11-1.git.0.6696e29.el7 will be installed --> Finished Dependency Resolution Dependencies Resolved Additional info: Adding Requires: docker < 1.9 to atomic-openshift-node will prevent this problem from happening.
*** Bug 1323057 has been marked as a duplicate of this bug. ***
According to comment 4, re-test it with atomic-openshift-node-3.1.1.6-5.git.35.0742c54.el7aos.x86_64, still failed. On a system without docker pre-installed, enable rhel extra and ose-3.1 repo, install atomic-openshift-node, get the following error: # yum install atomic-openshift-node Loaded plugins: product-id, search-disabled-repos, subscription-manager This system is not registered to Red Hat Subscription Management. You can use subscription-manager to register. ose-v3 | 1.2 kB 00:00:00 Resolving Dependencies --> Running transaction check ---> Package atomic-openshift-node.x86_64 0:3.1.1.6-5.git.35.0742c54.el7aos will be installed --> Processing Dependency: tuned-profiles-atomic-openshift-node = 3.1.1.6-5.git.35.0742c54.el7aos for package: atomic-openshift-node-3.1.1.6-5.git.35.0742c54.el7aos.x86_64 --> Processing Dependency: atomic-openshift = 3.1.1.6-5.git.35.0742c54.el7aos for package: atomic-openshift-node-3.1.1.6-5.git.35.0742c54.el7aos.x86_64 --> Processing Dependency: docker-io < 1.9 for package: atomic-openshift-node-3.1.1.6-5.git.35.0742c54.el7aos.x86_64 --> Processing Dependency: docker-io >= 1.8.2 for package: atomic-openshift-node-3.1.1.6-5.git.35.0742c54.el7aos.x86_64 --> Running transaction check ---> Package atomic-openshift.x86_64 0:3.1.1.6-5.git.35.0742c54.el7aos will be installed --> Processing Dependency: atomic-openshift-clients = 3.1.1.6-5.git.35.0742c54.el7aos for package: atomic-openshift-3.1.1.6-5.git.35.0742c54.el7aos.x86_64 ---> Package docker.x86_64 0:1.5.0-28.el7 will be installed --> Processing Dependency: docker-io < 1.9 for package: atomic-openshift-node-3.1.1.6-5.git.35.0742c54.el7aos.x86_64 ---> Package docker.x86_64 0:1.9.1-25.el7 will be installed --> Processing Dependency: docker-forward-journald = 1.9.1-25.el7 for package: docker-1.9.1-25.el7.x86_64 --> Processing Dependency: docker-selinux >= 1.9.1-25.el7 for package: docker-1.9.1-25.el7.x86_64 ---> Package tuned-profiles-atomic-openshift-node.x86_64 0:3.1.1.6-5.git.35.0742c54.el7aos will be installed --> Running transaction check ---> Package atomic-openshift-clients.x86_64 0:3.1.1.6-5.git.35.0742c54.el7aos will be installed ---> Package docker.x86_64 0:1.5.0-28.el7 will be installed --> Processing Dependency: docker-io < 1.9 for package: atomic-openshift-node-3.1.1.6-5.git.35.0742c54.el7aos.x86_64 ---> Package docker-forward-journald.x86_64 0:1.9.1-25.el7 will be installed ---> Package docker-selinux.x86_64 0:1.9.1-25.el7 will be installed --> Processing Conflict: docker-1.9.1-25.el7.x86_64 conflicts atomic-openshift < 3.2 --> Finished Dependency Resolution Error: Package: atomic-openshift-node-3.1.1.6-5.git.35.0742c54.el7aos.x86_64 (ose-v3) Requires: docker-io < 1.9 Available: docker-1.2.0-1.8.el7.x86_64 (rhel-7-extra) docker-io Available: docker-1.3.2-4.el7.x86_64 (rhel-7-extra) docker-io = 1.3.2 Available: docker-1.4.1-37.el7.x86_64 (rhel-7-extra) docker-io = 1.4.1-37.el7 Available: docker-1.5.0-27.el7.x86_64 (rhel-7-extra) docker-io = 1.5.0-27 Available: docker-1.5.0-28.el7.x86_64 (rhel-7-extra) docker-io = 1.5.0-28 Available: docker-1.6.0-11.el7.x86_64 (rhel-7-extra) docker-io = 1.6.0-11 Available: docker-1.6.2-14.el7.x86_64 (rhel-7-extra) docker-io = 1.6.2-14 Available: docker-1.7.1-108.el7.x86_64 (rhel-7-extra) docker-io = 1.7.1-108.el7 Available: docker-1.7.1-115.el7.x86_64 (rhel-7-extra) docker-io = 1.7.1-115.el7 Available: docker-1.8.2-7.el7.x86_64 (rhel-7-extra) docker-io = 1.8.2-7.el7 Available: docker-1.8.2-8.el7.x86_64 (rhel-7-extra) docker-io = 1.8.2-8.el7 Available: docker-1.8.2-10.el7.x86_64 (rhel-7-extra) docker-io = 1.8.2-10.el7 Installing: docker-1.9.1-25.el7.x86_64 (docker-19) docker-io = 1.9.1-25.el7 Available: docker-0.11.1-19.el7.x86_64 (rhel-7-extra) Not found Available: docker-0.11.1-22.el7.x86_64 (rhel-7-extra) Not found Available: docker-1.1.2-13.el7.x86_64 (rhel-7-extra) Not found Error: docker conflicts with atomic-openshift-3.1.1.6-5.git.35.0742c54.el7aos.x86_64 You could try using --skip-broken to work around the problem You could try running: rpm -Va --nofiles --nodigest In comment 4, you are installing ose 3.2 node rpm package, not ose 3.1 node rpm packages. > --> Running transaction check > ---> Package atomic-openshift.x86_64 0:3.2.0.11-1.git.0.6696e29.el7 will be > installed > --> Processing Dependency: atomic-openshift-clients = > 3.2.0.11-1.git.0.6696e29.el7 for package: > atomic-openshift-3.2.0.11-1.git.0.6696e29.el7.x86_64 > ---> Package docker.x86_64 0:1.9.1-25.el7 will be installed > ---> Package tuned-profiles-atomic-openshift-node.x86_64 > 0:3.2.0.11-1.git.0.6696e29.el7 will be installed > --> Running transaction check > ---> Package atomic-openshift-clients.x86_64 0:3.2.0.11-1.git.0.6696e29.el7 > will be installed > --> Finished Dependency Resolution
I'm afraid this actually cannot be fixed based on http://www.rpm.org/wiki/PackagerDocs/BooleanDependencies but i'm trying a few other things.
Other than implementing version lock in yum, is there any other suggested work-arounds to this?
(In reply to Peter Larsen from comment #9) > Other than implementing version lock in yum, is there any other suggested > work-arounds to this? You're talking about running `yum upgrade` after the installation is complete? If so, no, version lock will work but beware that it means you'll never be made aware of a security update for docker after you enable that.
(In reply to Scott Dodson from comment #10) > (In reply to Peter Larsen from comment #9) > > Other than implementing version lock in yum, is there any other suggested > > work-arounds to this? > > You're talking about running `yum upgrade` after the installation is > complete? If so, no, version lock will work but beware that it means you'll > never be made aware of a security update for docker after you enable that. I have the same problem installing - the docker conflict comes up every time atomic-openshift is attempted to be install with the current repo configuration. I presume we can use "exclude=" in the yum.conf configuration too, but that too would have to be adjusted once this bug has been resolved. The configuration could be managed using a simple ansible script? Are there any better work-arounds to this?
(In reply to Peter Larsen from comment #11) > I have the same problem installing - the docker conflict comes up every time > atomic-openshift is attempted to be install with the current repo > configuration. I presume we can use "exclude=" in the yum.conf configuration > too, but that too would have to be adjusted once this bug has been resolved. > The configuration could be managed using a simple ansible script? > > Are there any better work-arounds to this? Have you updated your installer? We shipped an updated installer that should avoid this. If the currently released installer is failing lets open a separate bug on that.
(In reply to Scott Dodson from comment #12) > (In reply to Peter Larsen from comment #11) > > I have the same problem installing - the docker conflict comes up every time > > atomic-openshift is attempted to be install with the current repo > > configuration. I presume we can use "exclude=" in the yum.conf configuration > > too, but that too would have to be adjusted once this bug has been resolved. > > The configuration could be managed using a simple ansible script? > > > > Are there any better work-arounds to this? > > Have you updated your installer? We shipped an updated installer that should > avoid this. If the currently released installer is failing lets open a > separate bug on that. Using openshift-ansible-playbooks-3.0.47-1.git.0.4498ce3.el7aos.noarch Results in the same issue: TASK: [openshift_common | Install the base package for versioning] ************ failed: [node3.rhsademo.net] => {"changed": true, "rc": 1, "results": ["Loaded plugins: langpacks, search-disabled-repos\nResolving Dependencies\n--> Running transaction check\n---> Package atomic-openshift.x86_64 0:3.1.1.6-4.git.32.adf8ec9.el7aos will be installed\n--> Processing Dependency: atomic-openshift-clients = 3.1.1.6-4.git.32.adf8ec9.el7aos for package: atomic-openshift-3.1.1.6-4.git.32.adf8ec9.el7aos.x86_64\n--> Running transaction check\n---> Package atomic-openshift-clients.x86_64 0:3.1.1.6-4.git.32.adf8ec9.el7aos will be installed\n--> Processing Conflict: docker-1.9.1-25.el7.x86_64 conflicts atomic-openshift < 3.2\n--> Finished Dependency Resolution\n You could try using --skip-broken to work around the problem\n You could try running: rpm -Va --nofiles --nodigest\n"]} msg: Error: docker conflicts with atomic-openshift-3.1.1.6-4.git.32.adf8ec9.el7aos.x86_64
What we just shipped to fix this bug is openshift-ansible-3.0.47-6.git.0.7e39163.el7aos, could you have try to update your installer?
(In reply to Johnny Liu from comment #14) > What we just shipped to fix this bug is > openshift-ansible-3.0.47-6.git.0.7e39163.el7aos, could you have try to > update your installer? $ sudo repoquery openshift-ansible openshift-ansible-0:3.0.47-1.git.0.4498ce3.el7aos.noarch Sorry - not available.
The latest update on this is that the 3.2 installer (which will be compatible will 3.0 and 3.1) will ensure the correct version of Docker is running for OSE. Bug #1324130 will handle the removal of the rpm conflicts.