+++ This bug was initially created as a clone of Bug #1538806 +++ Description of problem: When users perform an openshift-ansible install with containerized components and customize the image names by setting osn_image, osn_ovs_image, osm_image, or osm_etcd_image variables, the docker_image_availability check is still looking for the default component images. Expected results: This check should be looking for the images that the actual install will attempt to use. --- Additional comment from Luke Meyer on 2018-01-25 16:39:17 EST --- As reported in https://github.com/openshift/openshift-ansible/issues/6720 and https://github.com/openshift/openshift-ansible/issues/5330 Fix against current master is under way at https://github.com/openshift/openshift-ansible/pull/6880
3.7 backport is https://github.com/openshift/openshift-ansible/pull/6901
Verified in openshift-ansible-3.7.27-1.git.0.ae95fc3.el7.noarch.rpm With osn_ovs_image, osn_image and osm_image set to the inexistent images, installer failed as expected.
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-2018:0636