Bug 1384059

Summary:	Ansible installation forced to use registry.access.redhat.com
Product:	OpenShift Container Platform	Reporter:	Alexander Koksharov <akokshar>
Component:	Installer	Assignee:	Tim Bielawa <tbielawa>
Status:	CLOSED DEFERRED	QA Contact:	Johnny Liu <jialiu>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	3.3.0	CC:	akokshar, aos-bugs, jokerman, mmccomas
Target Milestone:	---	Flags:	tbielawa: needinfo? (akokshar) tbielawa: needinfo? (akokshar)
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	No Doc Update
Doc Text:	undefined	Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-01-05 17:47:33 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:

Description Alexander Koksharov 2016-10-12 12:48:18 UTC

Description of problem:

We did add an 'additional_registries' entry in ansible inventory:
openshift_docker_additional_registries=xxx
openshift_docker_insecure_registries=xxx
openshift_docker_blocked_registries=xxx

However, default "registry.access.redhat.com" is added as a resource for the registry.

Version-Release number of selected component (if applicable):
3.3

How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Tim Bielawa 2016-10-20 19:55:18 UTC

Alexander,

The bug report says 

> However, default "registry.access.redhat.com" is added as a resource for the registry.

I'm not sure what the exact issue is here. Are the additional registries not being added?

Comment 2 Alexander Koksharov 2016-10-24 14:04:39 UTC

This is unwanted behavior, Customer only want to use their own internal registry (via Satellite). The problem is that "registry.access.redhat.com" is forcibly configured even when custom registry address is defined.

Comment 3 Tim Bielawa 2016-10-24 15:36:56 UTC

Alexander,

We've looked into this and figured out what's going on. The openshift_docker_* parameters by themselves are not sufficient to change the **default** registry. They add **additional** registries, block registries, and label insecure registries.

To accomplish what the customer is asking for you need to use some more parameters.

Replace <REG_HOSTNAME> with the hostname of the docker image registry and <PORT> with the access port to the registry. The "${component}" and "${version}" strings below must not be changed:

> oreg_url=<REG_HOSTNAME>:<PORT>/openshift3/ose-${component}:${version}

This sets the default registry URL.

> openshift_docker_additional_registries=<REG_HOSTNAME>:<PORT>
> openshift_docker_insecure_registries=<REG_HOSTNAME>:<PORT>

These configure docker with additional registries.

> openshift_examples_modify_imagestreams=true

This changes the default registry URL in our image templates to use the registry provided by **oreg_url**.

For example, in a playbook if the customers registry was registry.example.com and listened on port 8888, then their **hosts** file would have this content:

> [OSEv3:vars]
>
> oreg_url=registry.example.com:8888/openshift3/ose-${component}:${version}
> openshift_docker_additional_registries=registry.example.com:8888
> openshift_docker_insecure_registries=registry.example.com:8888
> openshift_examples_modify_imagestreams=true


Please let us know if this fixes the customers issue. Thanks!

Comment 4 Tim Bielawa 2016-12-15 18:07:34 UTC

Has the information I provided resolved the issue for the customer?

Comment 5 Tim Bielawa 2017-01-05 17:16:24 UTC

Upstream support case has been resolved. Customer has responded:

> I think this issue can be solved, by adding the oreg_url in our hosts file as described. I've added soms new nodes and the newly added nodes took the correct url.
> Thanks!