051e05a91d
Currently we use the following command to determine if rabbit is up and running *and* ready to service requests: rabbitmqctl eval "rabbit_mnesia:is_clustered()." | grep -q true Now we have occasionally observed that rabbitmqctl policies commands which are executed after said exec['rabbitmq-ready'] will fail. One potential reason is that is_clustered() can return true *before* the rabbit app is actually running. In fact we can see it does return true even though the app is stopped: ()[root@controller-1 /]$ rabbitmqctl stop_app Stopping rabbit application on node rabbit@controller-1 ... ()[root@controller-1 /]$ rabbitmqctl eval 'rabbit_mnesia:is_clustered().' true Let's switch to a combination of commands that check for the cluster to be up *and* the rabbitmq app to be running: ()[root@controller-1 /]$ rabbitmqctl stop_app Stopping rabbit application on node rabbit@controller-1 ... ()[root@controller-1 /]$ rabbitmqctl eval 'rabbit_nodes:is_running(node(), rabbit).' false Suggested-By: Bogdan Dobrelya <bdobreli@redhat.com> Closes-Bug: #1835615 Change-Id: I29f779145a39cd16374a91626f7fae1581a18224 |
||
---|---|---|
files | ||
lib | ||
manifests | ||
releasenotes | ||
spec | ||
templates | ||
zuul.d | ||
.gitignore | ||
.gitreview | ||
.sync.yml | ||
Gemfile | ||
LICENSE | ||
Puppetfile_extras | ||
README.md | ||
Rakefile | ||
bindep.txt | ||
metadata.json | ||
setup.cfg | ||
setup.py | ||
test-requirements.txt | ||
tox.ini |
README.md
Team and repository tags
puppet-tripleo
Lightweight composition layer for Puppet TripleO.
Contributing
- Free software: Apache License (2.0)
- Source: http://git.openstack.org/cgit/openstack/puppet-tripleo
- Bugs: http://bugs.launchpad.net/tripleo (tag: puppet)
- Documentation: