RabbitMQ reconfigure fails with 'rabbitmq_confs' undefined

[Mark Goddard]

Since https://review.openstack.org/#/c/523208/, rabbitmq deployment can fail with an undefined variable reference to 'rabbitmq_confs'. This happens if the handler is triggered and config.json has not changed.

[Mark Goddard (mgoddard)]

Fix proposed here: https://review.openstack.org/637199

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/637199
Committed: https://git.openstack.org/cgit/openstack/kolla-ansible/commit/?id=1e2a1a8fe12cd34abe904bbaca652884529f6f9a
Submitter: Zuul
Branch: master

commit 1e2a1a8fe12cd34abe904bbaca652884529f6f9a
Author: Mark Goddard <email address hidden>
Date: Fri Feb 15 14:45:33 2019 +0000

    Fix rabbitmq reconfigure, simplify role

    Since Id724b44a3edd951fa8b06c9f2c347e9ed8c5ffd9, there is a reference to a
    non-existent variable, rabbitmq_confs, that causes deployment to fail if
    rabbitmq configuration other than config.json is changed.

    I'm taking this opportunity to simplify the role, since we can use the Ansible
    handler notification system to determine when handlers need to run, without
    registering and checking variables. This simpler approach was used in the
    haproxy refactor.

    Change-Id: Ibe0e7fda93afff741243ff9c350db1c8c6e1e6d3
    Closes-Bug: #1816053

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/kolla-ansible 8.0.0.0rc1 release candidate.