Skip to content

Clarify which exchanges should remain after the forced reset of RabbitMQ #420

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Mar 2, 2023
Merged

Clarify which exchanges should remain after the forced reset of RabbitMQ #420

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
af2dcdb
Clarify which exchanges should remain after the forced reset of RabbitMQ
MoteHue Mar 1, 2023
51017f8
Update doc/source/operations/rabbitmq.rst
MoteHue Mar 1, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions doc/source/operations/rabbitmq.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -128,6 +128,8 @@ Check to see if all OpenStack queues and exchanges have been removed from the Ra
kayobe overcloud host command run --limit controllers --show-output --command 'docker exec rabbitmq rabbitmqctl list_queues name'
kayobe overcloud host command run --limit controllers --show-output --command 'docker exec rabbitmq rabbitmqctl list_exchanges name'

There should be no queues listed, and the only exchanges listed should start with `amq.`.

Start the OpenStack services which use RabbitMQ. Note that this will start all
matching services, even if they weren't running prior to starting this
procedure.
Expand Down