Bug 1607276

Summary:	All existing amphora instances are deleting when RabbitMQ is down
Product:	Red Hat OpenStack	Reporter:	Carlos Goncalves <cgoncalves>
Component:	openstack-octavia	Assignee:	Carlos Goncalves <cgoncalves>
Status:	CLOSED ERRATA	QA Contact:	Alexander Stafeyev <astafeye>
Severity:	high	Docs Contact:
Priority:	high
Version:	13.0 (Queens)	CC:	akrzos, bbonguar, cgoncalves, hfukumot, ihrachys, lpeer, majopela, yohmura
Target Milestone:	z5	Keywords:	Triaged, ZStream
Target Release:	13.0 (Queens)
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	openstack-octavia-2.0.2-5.el7ost	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:
Clones:	1634986 (view as bug list)		Environment:
Last Closed:	2019-03-14 13:33:12 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:
Bug Depends On:
Bug Blocks:	1571507

Description Carlos Goncalves 2018-07-23 07:47:06 UTC

Description of problem:

All existing amphora instances are unexpectedly deleted when RabbitMQ is accidentally down.

Unfortunately, delete requests will fail because RabbitMQ is down, and then all amphora instances cannot be failed over. Recovery of amphorae cannot is not possible without recreating all load balancers.

This is a critical bug and we have to avoid this critical situation even when  RabbitMQ is not operational.


How reproducible:
100%

Steps to Reproduce:
1. configure octavia to use a queue_event_streamer
2. create load balancers
3. shutdown RabbitMQ
4. wait a few seconds/minutes


Actual results: all amphorae get deleted


Expected results: all amphorae would continue running


Additional info: this bug was first raised upstream: https://storyboard.openstack.org/#!/story/2002937

Comment 12 Carlos Goncalves 2018-10-01 19:45:46 UTC

Patch merged upstream in master. Backport to stable/queens under review now.

Comment 39 errata-xmlrpc 2019-03-14 13:33:12 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2019:0567