Bug 1465629 - cli_docker_*_registries don't apply in scaleup
cli_docker_*_registries don't apply in scaleup
Product: OpenShift Container Platform
Classification: Red Hat
Component: Installer (Show other bugs)
Unspecified Linux
unspecified Severity medium
: ---
: 3.6.z
Assigned To: Scott Dodson
Johnny Liu
Depends On:
  Show dependency treegraph
Reported: 2017-06-27 15:28 EDT by Sebastian Jug
Modified: 2017-07-20 13:40 EDT (History)
5 users (show)

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2017-07-20 13:40:58 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Sebastian Jug 2017-06-27 15:28:46 EDT
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:

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:
Comment 1 Scott Dodson 2017-07-20 10:33:30 EDT
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 11:06:14 EDT
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.