Hide Forgot
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:
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?
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.
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!
Has the information I provided resolved the issue for the customer?
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!