Description of problem:
This issue does not happen with openshift-ansible-3.9.2-1. So it is a regression bug.
The bug is introduced by dc5ff9724234b3d83470879c7ebb794ed7f3cdea;

But seem like it is already fixed by c69216d17595d37f4010160db15bf88b4d92fb52 in master branch.

Open this bug for tracking if PR would be landed into rpm package.

Version-Release number of the following components:
openshift-ansible-3.9.7-1.git.0.60d5c90.el7.noarch

How reproducible:
Always

Steps to Reproduce:
1. Set oreg_url to a non-default registry (not registry.access.redhat.com), and openshift_examples_modify_imagestreams=true.
2. Trigger installation.
3.

Actual results:
The following steps are skipped, which will lead registry-console pod is still pulling image from default official product registry.
<--snip-->
TASK [openshift_hosted_templates : Modify registry paths if registry_url is not registry.access.redhat.com] ***
Wednesday 14 March 2018  04:03:45 +0000 (0:00:00.146)       0:06:51.872 ******* 
skipping: [ec2-184-72-94-244.compute-1.amazonaws.com] => {"changed": false, "skip_reason": "Conditional result was False", "skipped": true}
<--snip-->

Expected results:
registry-console image should being pulled from non-default registry according to oreg_url setting.

Additional info:
Please attach logs from ansible-playbook with the -vvv flag