Description of problem: Upgrades for the use of docker 1.10 even thought docker 1.9 is supported. Version-Release number of selected component (if applicable): 3.1 > 3.2 How reproducible: 100% Steps to Reproduce: 1. Run upgrade script and set docker_upgrade=false Actual results: Upgrade fails because the upgrade script requires docker 1.10 Expected results: Upgrade should happen and not update docker to 1.10 Additional info: - fail: msg: This playbook requires access to Docker 1.10 or later when: g_docker_version.avail_version | default(g_docker_version.curr_version, true) | version_compare('1.10','<')
This PR should resolve this bug. https://github.com/openshift/openshift-ansible/pull/1945
The usage of "docker_version=1.9.1" in the host file also does not seem to help with this.
Can you check the version of the installer in use? This is believed to be fixed in the latest version of the 3.2 installer.
(In reply to Scott Dodson from comment #3) > Can you check the version of the installer in use? This is believed to be > fixed in the latest version of the 3.2 installer. atomic-openshift-utils-3.2.13-1.git.0.0afa976.el7.noarch
Fixed in https://github.com/openshift/openshift-ansible/pull/2285
Nevermind, not fixed.
Fixed in https://github.com/openshift/openshift-ansible/pull/2295, you can now override this requirement with either docker_version or docker_upgrade.
Can't install openshift-ansible-playbooks-3.3.30 [root@qe-upgrade-working host1]# dnf install atomic-openshift-utils Last metadata expiration check performed 0:02:03 ago on Sat Oct 8 01:49:35 2016. Error: nothing provides openshift-ansible-callback-plugins = 3.3.30 needed by openshift-ansible-playbooks-3.3.30-1.git.0.b260e04.el7.noarch (try to add '--allowerasing' to command line to replace conflicting packages)
Blocked by https://bugzilla.redhat.com/show_bug.cgi?id=1383189
docker_version still 1.9.1 after upgrade when We enabled docker-upgrade=false
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:2122