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
I think we should leave excluder in exclude mode for docker. Then as soon as Bug 1417723 is fixed we'll be fine. Right?
If comment 1 is true, then we should take this as a docs bug to remove unexcluding docker in the docs during upgrades.
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 ***