Bug 1715620

Summary:	When rebooting controllers one by one, rabbitmq gets in a splitbrain state and nothing work any longer
Product:	Red Hat OpenStack	Reporter:	David Hill <dhill>
Component:	rabbitmq-server	Assignee:	Peter Lemenkov <plemenko>
Status:	CLOSED DUPLICATE	QA Contact:	pkomarov
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	13.0 (Queens)	CC:	apevec, jeckersb, lhh, michele
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	All
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-05-31 09:26:11 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

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 ***