From c887a0a7d968c0326e0a475eb93cd5f20c3f2aa5 Mon Sep 17 00:00:00 2001
From: Ian Wienand <iwienand@redhat.com>
Date: Fri, 18 Nov 2022 16:20:48 +1100
Subject: [PATCH] Use prod_bastion group in gate bootstrap

This was missed in I137ab824b9a09ccb067b8d5f0bb2896192291883.

The called bootstrap playbook runs on prod_bastion[0], but we were
still calling the constructed gate group "bastion" (see note below on
what it's doing).

We don't notice because the multi-node setup is already making it so
the nodes can log into each other.  But it means we're not exercising
the root key addition role, which we should be doing in the gate.

Change-Id: I8238fc11a055c6d926b58df93c48a47121c0fde1
---
 playbooks/bootstrap-bridge.yaml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/playbooks/bootstrap-bridge.yaml b/playbooks/bootstrap-bridge.yaml
index 8191e2ad9c..6b781918bc 100644
--- a/playbooks/bootstrap-bridge.yaml
+++ b/playbooks/bootstrap-bridge.yaml
@@ -71,7 +71,7 @@
           copy:
             content: |
                 {{ inventory_hostname }}
-                [bastion]
+                [prod_bastion]
                 {{ inventory_hostname }}
             dest: '/home/zuul/bastion-inventory.ini'