From a481cb1be29ebc523cccac30ba5225b1a6bcadad Mon Sep 17 00:00:00 2001 From: Ian Wienand Date: Wed, 19 Oct 2022 16:29:22 +1100 Subject: [PATCH] bootstrap-bridge: use hostname for play The idea with this role is to install the root key from the on-disk RSA secret. However, when this play runs against localhost it doesn't match the host-variable defined root_rsa_key. This is being run nested -- the executor Ansible task has forked the Ansible we have installed on the bridge which is now installing this. "connection: local" does what we want here -- it makes ansible assume bridge.openstack.org is 127.0.0.1 -- which it is -- and avoids us having to worry about the bootstrap ssh-ing back to itself. This is a fixup for Iebaeed5028050d890ab541818f405978afd60124 Change-Id: I4cdcc373d1b7b6fa542a78c9f84067c79352d2f6 --- playbooks/zuul/run-production-bootstrap-bridge-add-rootkey.yaml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/playbooks/zuul/run-production-bootstrap-bridge-add-rootkey.yaml b/playbooks/zuul/run-production-bootstrap-bridge-add-rootkey.yaml index 3b64434a3c..f41c4f9315 100644 --- a/playbooks/zuul/run-production-bootstrap-bridge-add-rootkey.yaml +++ b/playbooks/zuul/run-production-bootstrap-bridge-add-rootkey.yaml @@ -1,4 +1,4 @@ -- hosts: localhost +- hosts: bridge.openstack.org connection: local tasks: - name: Install root keys