Bug 1425204 - Upgrades from 3.1 to 3.2 or 3.2 to 3.3 will update docker to latest version available.
Summary: Upgrades from 3.1 to 3.2 or 3.2 to 3.3 will update docker to latest version a...
Keywords:
Status: CLOSED DUPLICATE of bug 1417723
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Installer
Version: 3.2.1
Hardware: Unspecified
OS: Unspecified
unspecified
urgent
Target Milestone: ---
: ---
Assignee: Scott Dodson
QA Contact: Johnny Liu
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-02-20 20:11 UTC by Ryan Howe
Modified: 2017-03-02 21:30 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-03-02 21:30:24 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Ryan Howe 2017-02-20 20:11:43 UTC
Description of problem:

Upgrades from 3.1 to 3.2 or 3.2 to 3.3 will update docker to latest version available which is 1.12 currently. 1.12 is not supported on any of these versions. 



Version-Release number of selected component (if applicable):
3.1 
3.2 
3.3

How reproducible:
100%

Steps to Reproduce:
1. Run upgrade playbook from a 3.1 or 3.2 environment. 
2. Do not set docker_version in the hosts file  

Actual results:
Docker gets updated to 1.12


Expected results:
Docker gets updated to 1.10 (supported docker version) 




Additional info:

We only check for if docker version is >= 1.10

We set "docker_version" to the latest version found in the repos. 

https://github.com/openshift/openshift-ansible/blob/release-1.2/playbooks/common/openshift-cluster/upgrades/docker/upgrade_check.yml#L21-L28
https://github.com/openshift/openshift-ansible/blob/release-1.2/playbooks/common/openshift-cluster/upgrades/docker/upgrade_check.yml#L40-L42


We make sure that the excluder package is disabled so there is no exclude in the yum.conf. even with the exclude package enabled we would hit the issue because of bug : https://bugzilla.redhat.com/show_bug.cgi?id=1417723

Comment 1 Scott Dodson 2017-02-21 13:33:53 UTC
I think we should leave excluder in exclude mode for docker. Then as soon as Bug 1417723 is fixed we'll be fine. Right?

Comment 2 Scott Dodson 2017-02-21 13:34:33 UTC
If comment 1 is true, then we should take this as a docs bug to remove unexcluding docker in the docs during upgrades.

Comment 3 Scott Dodson 2017-03-02 21:30:24 UTC
Documentation actually does not advise the user to unexclude the docker excluder, so with 1417723 fixed this should no longer be an issue. Marking as a dupe of that bug.

*** This bug has been marked as a duplicate of bug 1417723 ***


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