rabbitmqctl list_channels timeout causes RabbitMQ restart
Affects | Status | Importance | Assigned to | Milestone | ||
---|---|---|---|---|---|---|
Mirantis OpenStack | Status tracked in 10.0.x | |||||
10.0.x |
Invalid
|
High
|
Alexey Galkin | |||
9.x |
Invalid
|
High
|
Alexey Galkin |
Bug Description
Detailed bug description:
BVT_2 build #197 failed with several messages in logs saying that AMQP server is unreachable (nova-all.log, neutron-all.log, neutron/
2016-04-
Also there are several messages saying that rabbitmqctl list_channels is timed out
2016-04-
RabbitMQ was restarted because of these timeouts and as a result the test failed.
Expected results:
RabbitMQ works seamlessly, test passes
Actual result:
RabbitMQ restarts, test fails
Reproducibility:
seen once in 197th build of BVT_2 task
See attachment for futher clarifications.
Changed in mos: | |
status: | New → Confirmed |
importance: | Undecided → High |
assignee: | nobody → MOS Oslo (mos-oslo) |
milestone: | none → 9.0 |
tags: | added: area-oslo |
summary: |
- RabbitMQ falls down with error "Error: unable to connect to node - 'rabbit@messaging-node-2': nodedown" + rabbitmqctl list_channels timeout causes RabbitMQ restart |
description: | updated |
Changed in mos: | |
milestone: | 9.0 → 9.0-updates |
(This check performed automatically)
Please, make sure that bug description contains the following sections filled in with the appropriate data related to the bug you are describing:
version
steps to reproduce
For more detailed information on the contents of each of the listed sections see https:/ /wiki.openstack .org/wiki/ Fuel/How_ to_contribute# Here_is_ how_you_ file_a_ bug