Bug 1436784

Summary: RabbitMQ - Termination of queue master fails with `{badmatch,{error,not_found}}`
Product: Red Hat OpenStack Reporter: Peter Lemenkov <plemenko>
Component: rabbitmq-serverAssignee: Peter Lemenkov <plemenko>
Status: CLOSED ERRATA QA Contact: Udi Shkalim <ushkalim>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 11.0 (Ocata)CC: apevec, jeckersb, lhh, mburns, plemenko, sclewis, slinaber, srevivo
Target Milestone: asyncKeywords: Triaged, ZStream
Target Release: 11.0 (Ocata)   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: rabbitmq-server-3.6.5-2.el7ost Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-06-15 16:56:30 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: 1441635, 1447355    
Attachments:
Description Flags
https://gist.github.com/jtaleric/81c7a3ea09636ca06f7f8d58164b1d5c none

Description Peter Lemenkov 2017-03-28 16:13:27 UTC 
Created attachment 1267032 [details]
https://gist.github.com/jtaleric/81c7a3ea09636ca06f7f8d58164b1d5c

Running some API Performance tests over the weekend against a single controller with 3 computes, RabbitMQ simply stopped working. Looking at RabbitMQ it doesn't seem to balloon in memory and hit OOM.. Issuing a pcs resource cleanup rabbitmq -- seems to have fixed the issue.

Logs contains a clear evidence of GH#1035 during shutting down.
Comment 5 Udi Shkalim 2017-06-07 13:52:57 UTC 
Verified on: rabbitmq-server-3.6.5-5.el7ost.noarch

After multiple restart and stop/start rabbitmq service with pcs commands no errors was found.
Comment 7 errata-xmlrpc 2017-06-15 16:56:30 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/RHBA-2017:1473