We need to wait for rabbitmq_ready exec so that rabbit is fully
up. This can only happen if we add the tag for it.
Also we need to make sure that launching the epmd process cannot
happen. The reason for this is the following:
When the puppet-rabbitmq module gets invoked (a simple facter run
will be sufficient) inside the rabbitmq_init_bundle container it spawns
an epmd process.
Now if we wait for the Exec[rabbitmq-ready], it means that this epmd
process is staying around until rabbit is up, but then will disappear
suddenly when the rabbitmq_init_bundle container exits, which will
subsequently confuse the rabbitmq cluster and make it fail.
Reviewed: https:/ /review. openstack. org/529470 /git.openstack. org/cgit/ openstack/ tripleo- heat-templates/ commit/ ?id=2baca3211a2 3dc723d9ffcf160 cad9e0c5ee4912
Committed: https:/
Submitter: Zuul
Branch: stable/pike
commit 2baca3211a23dc7 23d9ffcf160cad9 e0c5ee4912
Author: Michele Baldessari <email address hidden>
Date: Tue Dec 12 14:56:33 2017 +0100
Wait for rabbitmq_ready tag
We need to wait for rabbitmq_ready exec so that rabbit is fully init_bundle container it spawns ready], it means that this epmd init_bundle container exits, which will
up. This can only happen if we add the tag for it.
Also we need to make sure that launching the epmd process cannot
happen. The reason for this is the following:
When the puppet-rabbitmq module gets invoked (a simple facter run
will be sufficient) inside the rabbitmq_
an epmd process.
Now if we wait for the Exec[rabbitmq-
process is staying around until rabbit is up, but then will disappear
suddenly when the rabbitmq_
subsequently confuse the rabbitmq cluster and make it fail.
Partial-Bug: #1739026
Co-Authored-By: Damien Ciabrini <email address hidden>
Co-Authored-By: John Eckersberg <email address hidden>
Change-Id: Ie74a13a6c81819 48900ea0de8ee97 17f76f3ce79 667efc08825e4bc 7b1732f056)
(cherry picked from commit bab6ec25323fd9a