From 63728f40c97e87c83459822636b11a2b025f5f9f Mon Sep 17 00:00:00 2001
From: Jesse Pretorius <jesse.pretorius@rackspace.co.uk>
Date: Wed, 26 Sep 2018 19:38:36 +0100
Subject: [PATCH] Use loop_control for haproxy keystone back-end enablement

In I17dafb283e41ce05083ae4adb3a325aaca0253dd we switched the loop
control specification from in the common tasks to the parent task,
but forgot to implement the loop control for the task which enables
the back-end again later. This patch corrects that.

Change-Id: I0d7e4804bdc92ffe7a679060a686e684c01fcd1b
(cherry picked from commit 8d8755be86b6cde10f656de6ef19637a91b94954)
---
 playbooks/os-keystone-install.yml | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/playbooks/os-keystone-install.yml b/playbooks/os-keystone-install.yml
index 10873e61ff..20c310d139 100644
--- a/playbooks/os-keystone-install.yml
+++ b/playbooks/os-keystone-install.yml
@@ -134,9 +134,11 @@
     # to available again.
     - include: common-tasks/haproxy-endpoint-manage.yml
       vars:
-        haproxy_backend: "{{ item }}"
+        haproxy_backend: "{{ backend_name }}"
         haproxy_state: enabled
       when: "{{ groups['keystone_all'] | length > 1 }}"
+      loop_control:
+        loop_var: backend_name
       with_items:
         - "keystone_service-back"
         - "keystone_admin-back"