Bug 1465629 - cli_docker_*_registries don't apply in scaleup
Summary: cli_docker_*_registries don't apply in scaleup
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Installer
Version: 3.6.0
Hardware: Unspecified
OS: Linux
unspecified
medium
Target Milestone: ---
: 3.6.z
Assignee: Scott Dodson
QA Contact: Johnny Liu
URL:
Whiteboard: aos-scalability-36
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-06-27 19:28 UTC by Sebastian Jug
Modified: 2017-07-20 17:40 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-07-20 17:40:58 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Sebastian Jug 2017-06-27 19:28:46 UTC
Description of problem:
In our inventory we set cli_docker_additional_registries and
cli_docker_insecure_registries. These parameters work correctly during the advanced installer. When we try to use them with our openshift-node/scaleup, they are not applied to the nodes and the install will fail as the images are unable to be pulled.


Version-Release number of selected component (if applicable):
openshift-ansible git master


How reproducible:
Always


Steps to Reproduce:
1. Install OpenShift using advanced installer and specify cli_docker_*_registries parameters.
2. Add more nodes to the cluster by running openshift-node/scaleup with same base inventory.

Actual results:
Scaleup will fail as node images are unable to be pulled from default (non-custom) registry.

Expected results:
Scaleup will complete successfully as alternative registries set in inventory were added to docker.


Related issues:
https://bugzilla.redhat.com/show_bug.cgi?id=1331389

Comment 1 Scott Dodson 2017-07-20 14:33:30 UTC
Does this work when setting openshift_docker_additional_registries=registry.example.com instead? The variables you've mentioned were deprecated in the past.

Comment 2 Sebastian Jug 2017-07-20 15:06:14 UTC
I believe that's what we used to get it to work, yes.


Note You need to log in before you can comment on or make changes to this bug.