From 401c82ecc0b6cd3e51313faf681e8b75f0914234 Mon Sep 17 00:00:00 2001
From: wangqi <wang.qi@99cloud.net>
Date: Wed, 1 Aug 2018 11:42:01 +0000
Subject: [PATCH] Remove rabbit_max_retries option

The rabbit_max_retries parameter has been deprecated

Change-Id: I856a75faa4f55deb24265a7464581863c086c2a5
---
 templates/zun.conf.j2 | 6 ------
 1 file changed, 6 deletions(-)

diff --git a/templates/zun.conf.j2 b/templates/zun.conf.j2
index 3d0bbb7..93916ca 100644
--- a/templates/zun.conf.j2
+++ b/templates/zun.conf.j2
@@ -1742,12 +1742,6 @@ ssl = {{ zun_oslomsg_notify_use_ssl | bool }}
 # (integer value)
 #rabbit_interval_max = 30
 
-# DEPRECATED: Maximum number of RabbitMQ connection retries. Default is 0
-# (infinite retry count). (integer value)
-# This option is deprecated for removal.
-# Its value may be silently ignored in the future.
-#rabbit_max_retries = 0
-
 # Try to use HA queues in RabbitMQ (x-ha-policy: all). If you change this
 # option, you must wipe the RabbitMQ database. In RabbitMQ 3.0, queue mirroring
 # is no longer controlled by the x-ha-policy argument when declaring a queue.