RabbitMQ is down in staging #7817
Labels
No labels
announcement
authentication
automate
aws
backlog
blocked
bodhi
ci
Closed As
Duplicate
Closed As
Fixed
Closed As
Fixed with Explanation
Closed As
Initiative Worthy
Closed As
Insufficient data
Closed As
Invalid
Closed As
Spam
Closed As
Upstream
Closed As/Will Not
Can Not fix
cloud
communishift
copr
database
deprecated
dev
discourse
dns
downloads
easyfix
epel
factory2
firmitas
gitlab
greenwave
hardware
help wanted
high-gain
high-trouble
iad2
koji
koschei
lists
low-gain
low-trouble
mbs
medium-gain
medium-trouble
mini-initiative
mirrorlists
monitoring
Needs investigation
notifier
odcs
OpenShift
ops
OSBS
outage
packager_workflow_blocker
pagure
permissions
Priority
Needs Review
Priority
Next Meeting
Priority
🔥 URGENT 🔥
Priority
Waiting on Assignee
Priority
Waiting on External
Priority
Waiting on Reporter
rabbitmq
rdu-cc
release-monitoring
releng
repoSpanner
request-for-resources
s390x
security
SMTP
src.fp.o
staging
taiga
unfreeze
waiverdb
websites-general
wiki
No milestone
No project
No assignees
4 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: infrastructure/fedora-infrastructure#7817
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
I'm trying to run Bodhi's openshift playbook, and it fails with this error:
It is using the wrong host: rabbit@rabbitmq01.stg.phx2.fedoraproject.org, it should be using rabbitmq.stg.fedoraproject.org
Other apps have been adjusted: https://infrastructure.fedoraproject.org/cgit/ansible.git/commit/?id=1a09cff25c3afbabf9b4d2b7856827b5f334c1b1
This is the rabbitmq role that's failing; Bodhi's config file is not involved.
Should be fixed. It looks like it might be an ordering issue in our reboots... 01 came up and didn't find the others? will have to investigate...
[root@rabbitmq01 log][STG]# rabbitmqctl list_queues --online
Listing queues
test 0
should there be more queues?
You want probibly:
rabbitmqctl list_queues -p /pubsub --online
Listing queues
amqp_to_zmq 0
faf 0
the-new-hotness.stg 0
bodhi.stg_composer 0
bodhi.stg 2
federation: zmq.topic -> rabbit@rabbitmq01.stg.phx2.fedoraproject.org:/public_pubsub:zmq.topic 0
greenwave.stg 155175
amqp_bridge_verify_missing 0
federation: amq.topic -> rabbit@rabbitmq01.stg.phx2.fedoraproject.org:/public_pubsub:amq.topic 0
Yeah seems to be back now - thanks!
I landed a fix in our reboot playbook to restart these after reboots are done and the hosts are back.
Metadata Update from @kevin: