Description of problem:
If docker-1.13 is present on the repository, OpenShift health-check would check a higher docker version than requested and fail immediately. This is not reasonable because the higher docker version that installer checks may not what the user will use or install.
We already have atomic-openshift-docker-excluder that prevents from installing incorrect docker version, instead the OpenShift health check should check if the supported docker version is available on current repository.
Version-Release number of the following components:
Steps to Reproduce:
1. Trigger rpm installation on RHEL that have docker-1.12, docker-1.13 repo configured.
1. Hosts: qe-ghuang-master-etcd-xxx.qe.rhcloud.com, qe-ghuang-node-registry-router-xx.qe.rhcloud.com
Play: OpenShift Health Checks
Task: Run health checks (install) - EL
Message: One or more checks failed
Details: check "package_version":
Some required package(s) are available at a version
that is higher than requested
This will prevent installing the version you requested.
Please check your enabled repositories or adjust openshift_release.
If docker-1.12 is what we're going to support in 3.7, we just need to check if docker-1.12 is available on the host regardless of docker-1.13 or others.
Please attach logs from ansible-playbook with the -vvv flag
The obvious workaround while 3.6 and 3.7 are waiting for this fix is to disable the check with something like this in the inventory:
The installer should install the correct version anyway. However if you are installing docker prior to running an install, ensure that you have installed docker-1.12 and not docker-1.13 for these versions.
It turns out that the excluder *doesn't* currently exclude docker 1.13. That excluder update has been built for some time and should be released soon, but it will likely not help much. Refer to https://access.redhat.com/solutions/3376031 for how to proceed.
This bug may actually be to our benefit if it leads to users landing on that kbase.
This fix was shipped in openshift-ansible-3.7.42-1
*** Bug 1562098 has been marked as a duplicate of this bug. ***
*** Bug 1562099 has been marked as a duplicate of this bug. ***