From 2d036b6afdcd7958dae76fdd8b99849248a04470 Mon Sep 17 00:00:00 2001
From: Mark Goddard <mark@stackhpc.com>
Date: Wed, 20 Sep 2017 08:54:27 +0000
Subject: [PATCH] Apply RabbitMQ workaround for issue #14 to all overcloud
 hosts

In some scenarios the RabbitMQ services may be running on hosts other than the
controllers. For example, when there are separate database servers.
---
 ansible/overcloud-etc-hosts-fixup.yml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/ansible/overcloud-etc-hosts-fixup.yml b/ansible/overcloud-etc-hosts-fixup.yml
index d51e87741..9090a1037 100644
--- a/ansible/overcloud-etc-hosts-fixup.yml
+++ b/ansible/overcloud-etc-hosts-fixup.yml
@@ -19,7 +19,7 @@
       become: True
 
 - name: Ensure rabbitmq containers' /etc/hosts does not contain provisioning network IP
-  hosts: controllers
+  hosts: overcloud
   vars:
     rabbitmq_containers:
       - rabbitmq