Revert "Configure plugins and policies after RabbitMQ"

This is causing breakage outside of the gate for the AIO and
until that's worked out we should revert this. I think whatever
the intent of this patch was it needs a bit more time spend on
figuring out the right approach that works for single nodes
and clusters.

This reverts commit ab8cd85497.

Change-Id: I464cb658bd5695f0b1c031184bcd25d979a1a00d
This commit is contained in:
Jesse Pretorius (odyssey4me) 2018-04-19 14:52:20 +00:00
parent ab8cd85497
commit d44eb3b39a
1 changed files with 22 additions and 22 deletions

View File

@ -13,6 +13,28 @@
# See the License for the specific language governing permissions and
# limitations under the License.
- name: Configure rabbitmq plugins
rabbitmq_plugin:
names: "{{ item.name }}"
state: "{{ item.state }}"
with_items: "{{ rabbitmq_plugins }}"
register: rabbitmq_plugin
tags:
- rabbitmq-config
- name: Apply rabbitmq policies
rabbitmq_policy:
node: "rabbit@{{ ansible_hostname }}"
name: "{{ item.name }}"
pattern: "{{ item.pattern }}"
priority: "{{ item.priority | default(0) }}"
tags: "{{ item.tags }}"
register: rabbitmq_queue_mirror
with_items: "{{ rabbitmq_policies }}"
tags:
- rabbitmq-config
- rabbitmq-cluster
- name: Create rabbitmq systemd service config dir
file:
path: "/etc/systemd/system/rabbitmq-server.service.d"
@ -66,28 +88,6 @@
static: no
when: rabbit_config_changed|changed or rabbitmq_plugin|changed or rabbitmq_queue_mirror|changed
- name: Configure rabbitmq plugins
rabbitmq_plugin:
names: "{{ item.name }}"
state: "{{ item.state }}"
with_items: "{{ rabbitmq_plugins }}"
register: rabbitmq_plugin
tags:
- rabbitmq-config
- name: Apply rabbitmq policies
rabbitmq_policy:
node: "rabbit@{{ ansible_hostname }}"
name: "{{ item.name }}"
pattern: "{{ item.pattern }}"
priority: "{{ item.priority | default(0) }}"
tags: "{{ item.tags }}"
register: rabbitmq_queue_mirror
with_items: "{{ rabbitmq_policies }}"
tags:
- rabbitmq-config
- rabbitmq-cluster
# This is being done because the rabbitctl command used by the module
# is not very effective at returning proper status codes for failure
# and the module does not error detection. until we can go upstream