Bug 1607276 - All existing amphora instances are deleting when RabbitMQ is down
Summary: All existing amphora instances are deleting when RabbitMQ is down
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-octavia
Version: 13.0 (Queens)
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: z5
: 13.0 (Queens)
Assignee: Carlos Goncalves
QA Contact: Alexander Stafeyev
URL:
Whiteboard:
Depends On:
Blocks: 1571507
TreeView+ depends on / blocked
 
Reported: 2018-07-23 07:47 UTC by Carlos Goncalves
Modified: 2022-07-09 10:39 UTC (History)
8 users (show)

Fixed In Version: openstack-octavia-2.0.2-5.el7ost
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1634986 (view as bug list)
Environment:
Last Closed: 2019-03-14 13:33:12 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
OpenStack Storyboard 2002937 0 None None None 2018-07-23 07:47:06 UTC
OpenStack gerrit 581585 0 None master: MERGED octavia: Separate the thread pool for health and stats update (I576687f5b646496ff3a00787cf5e8c27f36b9448) 2018-12-03 10:30:52 UTC
OpenStack gerrit 607034 0 None stable/queens: NEW octavia: Separate the thread pool for health and stats update (I576687f5b646496ff3a00787cf5e8c27f36b9448) 2018-12-03 10:30:46 UTC
Red Hat Bugzilla 1618772 0 high CLOSED CPU load skyrocketing due to API and Health Manager not being able to connect to the bus 2022-09-23 17:41:18 UTC
Red Hat Issue Tracker OSP-17047 0 None None None 2022-07-09 10:39:20 UTC
Red Hat Product Errata RHSA-2019:0567 0 None None None 2019-03-14 13:33:19 UTC

Internal Links: 1618772

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


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