From 9d156eb005608fa822ff049a4cbd19890fd102f5 Mon Sep 17 00:00:00 2001
From: Vladislav Belogrudov <vladislav.belogrudov@oracle.com>
Date: Thu, 10 Sep 2015 13:22:00 +0300
Subject: [PATCH] First keepalived container is started with wrong priority

First keepalived container is started with priority 0 but the
latter should be in range 1-255. This gives error and keepalived
resumes with default priority 100.

Change-Id: Ib11d0072a96b818d86c81a32e78118c0c82b74d8
Closes-Bug: #1494237
---
 ansible/roles/haproxy/templates/keepalived.conf.j2 | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/ansible/roles/haproxy/templates/keepalived.conf.j2 b/ansible/roles/haproxy/templates/keepalived.conf.j2
index 232ff8e46c..01ddabafe5 100644
--- a/ansible/roles/haproxy/templates/keepalived.conf.j2
+++ b/ansible/roles/haproxy/templates/keepalived.conf.j2
@@ -9,7 +9,7 @@ vrrp_instance Floating {
     state MASTER
     interface {{ api_interface }}
     virtual_router_id 51
-    priority {{ groups['haproxy'].index(inventory_hostname) }}
+    priority {{ groups['haproxy'].index(inventory_hostname) + 1 }}
     advert_int 1
     virtual_ipaddress {
         {{ kolla_internal_address }}