Browse Source

Fix bug after portal_net move from master to common role.

Use of the variable was still pointing to the master role location
causing the default insecure registry subnet to be used rather than the
expected one.
Devan Goodwin 9 years ago
parent
commit
08403855c0
1 changed files with 2 additions and 2 deletions
  1. 2 2
      playbooks/common/openshift-node/config.yml

+ 2 - 2
playbooks/common/openshift-node/config.yml

@@ -119,7 +119,7 @@
     # hostvars[groups.oo_first_master.0].openshift.hosted.registry instead of
     # hardcoding
     openshift_docker_hosted_registry_insecure: True
-    openshift_docker_hosted_registry_network: "{{ hostvars[groups.oo_first_master.0].openshift.master.portal_net }}"
+    openshift_docker_hosted_registry_network: "{{ hostvars[groups.oo_first_master.0].openshift.common.portal_net }}"
   roles:
   - openshift_node
 
@@ -132,7 +132,7 @@
     # hostvars[groups.oo_first_master.0].openshift.hosted.registry instead of
     # hardcoding
     openshift_docker_hosted_registry_insecure: True
-    openshift_docker_hosted_registry_network: "{{ hostvars[groups.oo_first_master.0].openshift.master.portal_net }}"
+    openshift_docker_hosted_registry_network: "{{ hostvars[groups.oo_first_master.0].openshift.common.portal_net }}"
   roles:
   - openshift_node