Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1320695

Summary: For 3.1 and 3.0 installs prevent the installer from installing docker-1.9
Product: OpenShift Container Platform Reporter: Scott Dodson <sdodson>
Component: InstallerAssignee: Scott Dodson <sdodson>
Status: CLOSED ERRATA QA Contact: Ma xiaoqiang <xiama>
Severity: medium Docs Contact:
Priority: medium    
Version: 3.1.0CC: aos-bugs, jialiu, jkaur, jmatthew, jokerman, kurktchiev, mmccomas, mwoodson, plarsen, sdodson, xiama, xtian
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: openshift-ansible-3.0.47-6.git.0.7e39163.el7aos Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-04-06 12:42:58 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:

Description Scott Dodson 2016-03-23 18:17:14 UTC
Description of problem:
Docker 1.9 packages will have a conflicts on atomic-openshift < 3.2. We should avoid installing docker-1.9 when we're installing versions older than 3.2.

Version-Release number of selected component (if applicable):
openshift-ansible-3.0.47-1.git.0.4498ce3.el7aos.src.rpm

How reproducible:


Steps to Reproduce:
1. Add a docker-1.9 repo to your installation environment
2. Run the installer installing 3.1 or 3.0
3. 

Actual results:
Installation conflicts, failed installation.


Expected results:
Successful installation

Additional info:
Exact failure is 
TASK: [docker | Install docker] ***********************************************
failed: [ose3-master.example.com] => {"changed": true, "rc": 1, "results": ["Loaded plugins: search-disabled-repos\nResolving Dependencies\n--> Running transaction check
\n---> Package docker.x86_64 0:1.9.1-19.el7 will be installed\n--> Processing Conflict: atomic-openshift-clients-3.1.1.6-4.git.27.478f750.el7.x86_64 conflicts docker = 1
.9.1\n--> Processing Conflict: atomic-openshift-clients-3.1.1.6-4.git.27.478f750.el7.x86_64 conflicts docker = 1.9.1\n--> Processing Conflict: atomic-openshift-3.1.1.6-4
.git.27.478f750.el7.x86_64 conflicts docker = 1.9.1\n--> Processing Conflict: atomic-openshift-3.1.1.6-4.git.27.478f750.el7.x86_64 conflicts docker = 1.9.1\n--> Processi
ng Conflict: docker-1.9.1-19.el7.x86_64 conflicts atomic-openshift < 3.2\n--> Finished Dependency Resolution\n You could try using --skip-broken to work around the probl
em\n You could try running: rpm -Va --nofiles --nodigest\n"]}
msg: Repository 'bob' is missing name in configuration, using id
Repository 'rhel-7-extras-nightly' is missing name in configuration, using id
Error: docker conflicts with atomic-openshift-3.1.1.6-4.git.27.478f750.el7.x86_64
Error: atomic-openshift conflicts with docker-1.9.1-19.el7.x86_64
Error: atomic-openshift-clients conflicts with docker-1.9.1-19.el7.x86_64

Comment 2 Ma xiaoqiang 2016-03-24 07:32:10 UTC
Check on openshift-ansible-3.0.64-1.git.0.6df4b9a.el7.noarch

scenario 1. install containerized env with ose-3.1.1.6 on atomic
pass

scenario 2. Install RPM env with ose-3.1.1.6 on RHEL
1. Add a docker-1.9 repo to server
2. install ose-3.1.1.6
result:
docker-1.8.2, docker-selinux-1.9.1-16.el7.x86_64

scenario 3. Install RPM with ose-3.2
1. Add a docker-1.9 repo to server
2. install ose-3.2
result:
docker-1.9.1, docker-selinux-1.9.1-16.el7.x86_64

scenario 4. Install RPM with ose-3.0
1. Add a docker-1.9 repo to server
2. install ose-3.2
result:
docker-1.8.2-10.el7.x86_64
docker-selinux-1.9.1-19.el7.x86_64

Move this issue to VERIFIED

Comment 5 Scott Dodson 2016-03-30 03:25:57 UTC
This should also now downgrade if docker-1.9 is installed but you're installing OpenShift 3.0 or 3.1.

Comment 11 Ma xiaoqiang 2016-03-31 02:49:43 UTC
check on openshift-ansible-3.0.47-4.git.0.33bd81d.el7aos.noarch
met the same errors in comment#7

Comment 16 Ma xiaoqiang 2016-04-01 02:41:13 UTC
Check on openshift-ansible-3.0.47-5.git.0.ac7e014.el7aos.noarch

Scenario 1
Install ose-3.1.1.6 with docker-1.9 on the rhel
check the version on all servers
#rpm -qa|grep docker
docker-selinux-1.9.1-19.el7.x86_64
docker-forward-journald-1.9.1-19.el7.x86_64
docker-1.8.2-10.el7.x86_64
# openshift version
openshift v3.1.1.6-33-g81eabcc
kubernetes v1.1.0-origin-1107-g4c8e6f4
etcd 2.1.2


Scenario 2
Install ose-3.0.2.0 with docker-1.9 on the rhel
check the version on all server
# rpm -qa| grep  docker
docker-selinux-1.9.1-19.el7.x86_64
docker-forward-journald-1.9.1-19.el7.x86_64
docker-1.8.2-10.el7.x86_64
# openshift version
openshift v3.0.2.0-45-g423f434
kubernetes v1.1.0-alpha.0-1605-g44c91b1

Scenario 3
Install ha-master ose-3.1 with docker-1.9 on the rhel
Met the same error in comment#7
It fail when configure 'openshift-master' role on the second master, I check the dependencies of the 'openshift-master' role.
- docker
- openshif_common
  - os_firewall 
  - openshift_facts
  - openshift_repos
  - docker#2
- openshift_cli
  - docker#3
  - openshif_common#2
the executed order is: docker-> os_firewall -> openshift_facts ->  openshift_repos -> docker#2(skip, duplicated with docker) -> openshif_common -> docker#3(skip, duplicated with docker) -> openshif_common#2(skip, duplicated with openshif_common) -> openshift_cli -> openshift_master

so ansible will install docker before configuring openshift repo on the second master, it will not downgrade the docker.

Comment 18 Ma xiaoqiang 2016-04-05 04:10:53 UTC
Check on  openshift-ansible-3.0.47-6.git.0.7e39163.el7aos.noarch


Scenario 3
Install ha-master ose-3.1 with docker-1.9 on the rhel
# rpm -qa|grep docker
docker-selinux-1.9.1-25.el7.x86_64
docker-1.8.2-10.el7.x86_64
docker-forward-journald-1.9.1-25.el7.x86_64

Install env successfully.

Comment 20 errata-xmlrpc 2016-04-06 12:42:58 UTC
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://access.redhat.com/errata/RHBA-2016:0602

Comment 21 Scott Dodson 2016-04-12 21:36:15 UTC
*** Bug 1326495 has been marked as a duplicate of this bug. ***