Bug 1715620 - When rebooting controllers one by one, rabbitmq gets in a splitbrain state and nothing work any longer
Summary: When rebooting controllers one by one, rabbitmq gets in a splitbrain state an...
Keywords:
Status: CLOSED DUPLICATE of bug 1592528
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: rabbitmq-server
Version: 13.0 (Queens)
Hardware: x86_64
OS: All
unspecified
medium
Target Milestone: ---
: ---
Assignee: Peter Lemenkov
QA Contact: pkomarov
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-05-30 19:48 UTC by David Hill
Modified: 2019-06-02 02:33 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-05-31 09:26:11 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Knowledge Base (Solution) 3366271 0 None None Instance creation not working in OSP12 [rabbitmq errors] 2019-06-02 02:33:48 UTC

Description David Hill 2019-05-30 19:48:09 UTC
Description of problem:
When rebooting controllers one by one, rabbitmq gets in a splitbrain state and nothing work any longer until rabbitmq-bundle is restarted and nova-computes containers are restarted.

Version-Release number of selected component (if applicable):
(undercloud) [stack@undercloud-0-rhosp13 ~]$ cat local_registry_images.yaml  | grep rabbit
- imagename: registry.access.redhat.com/rhosp13/openstack-rabbitmq:13.0-74


How reproducible:
Always

Steps to Reproduce:
1. Reboot controllers one by one
2. Try creating a VM
3.

Actual results:
Fails

Expected results:
Succeds

Additional info:
This appears to be consistent for many customers.

Comment 1 Michele Baldessari 2019-05-31 09:26:11 UTC

*** This bug has been marked as a duplicate of bug 1592528 ***


Note You need to log in before you can comment on or make changes to this bug.