Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1528401

Summary: Fails docker_images_availability with the installer playbook for ansible
Product: OpenShift Container Platform Reporter: Raul Mahiques <rmahique>
Component: InstallerAssignee: Luke Meyer <lmeyer>
Status: CLOSED DUPLICATE QA Contact: Johnny Liu <jialiu>
Severity: high Docs Contact:
Priority: unspecified    
Version: 3.7.1CC: aos-bugs, jokerman, mmccomas, xtian
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-01-12 19:27:39 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Raul Mahiques 2017-12-21 18:54:48 UTC 
Description of problem:
when doing the preflight chekcings with ansible playbook the check for docker_images_availability fails in environments which require a proxy to connect to registry.access.redhat.com. This is because the proxy parameters aren't passed to skopeo

The images can be retrieved using docker (configured to use the proxy)



Version-Release number of the following components:
rpm -q openshift-ansible
3.7.14-1.git.0.4b35b2d
rpm -q ansible
2.3.2.0-2
ansible --version
2.3.2.0

How reproducible:

Always

Steps to Reproduce:

1. add the variables:
  openshift_http_proxy and openshift_https_proxy to your inventory.
2. ansible-playbook /usr/share/ansible/openshift-ansible/playbooks/byo/config.yml




Actual results:
It will complain it cannot find the docker images and therefore fail.

Expected results:
It finds the docker images.
Comment 2 Luke Meyer 2018-01-12 19:27:39 UTC 
Agreed it's a problem; I believe it's a duplicate and will hopefully be addressed via https://github.com/openshift/openshift-ansible/pull/6716

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