From d3ca7e0aff94ff066e2f17702adca7a1ac20285f Mon Sep 17 00:00:00 2001 From: Maciej Wereski Date: Wed, 28 Jul 2021 13:13:47 +0000 Subject: noheat deployment: use nfs0 as nexus3 bastion Bastion rules may cause DNS malfunction sometimes. It won't be an issue on NFS server but might be on control or operator host. Issue-ID: INT-1601 Signed-off-by: Maciej Wereski Change-Id: I23f49a20257c34475ed02f4c0df036f0ded450f4 --- deployment/noheat/cluster-rke/ansible/create.yml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'deployment/noheat/cluster-rke/ansible/create.yml') diff --git a/deployment/noheat/cluster-rke/ansible/create.yml b/deployment/noheat/cluster-rke/ansible/create.yml index 7304dbb6c..296bb9536 100644 --- a/deployment/noheat/cluster-rke/ansible/create.yml +++ b/deployment/noheat/cluster-rke/ansible/create.yml @@ -5,7 +5,7 @@ roles: - role: setup_nfs - name: Set up bastion node for ONAP Docker registry - hosts: "control0" + hosts: "nfs0" become: yes roles: - role: create_bastion @@ -17,6 +17,6 @@ - name: Add cluster hostnames to /etc/hosts file lineinfile: path: /etc/hosts - line: "{{ hostvars['control0']['ansible_default_ipv4']['address'] }} {{ item }}" + line: "{{ hostvars['nfs0']['ansible_default_ipv4']['address'] }} {{ item }}" loop: - "nexus3.onap.org" -- cgit 1.2.3-korg