Bug 1382524

Summary: [upgrades] Clear out qpid event queue upon upgrade
Product: Red Hat Satellite Reporter: Mike McCune <mmccune>
Component: UpgradesAssignee: Chris Roberts <chrobert>
Status: CLOSED ERRATA QA Contact: Peter Ondrejka <pondrejk>
Severity: high Docs Contact:
Priority: high    
Version: 6.2.0CC: bbuckingham, bkearney, chrobert, jcallaha, pmoravec, zhunting
Target Milestone: UnspecifiedKeywords: PrioBumpField, Triaged
Target Release: Unused   
Hardware: x86_64   
OS: Linux   
URL: http://projects.theforeman.org/issues/16863
Whiteboard:
Fixed In Version: katello-installer-base-3.0.0.64-1 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
: 1394358 (view as bug list) Environment:
Last Closed: 2016-12-12 17:14:13 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: 1394358    

Description Mike McCune 2016-10-06 22:48:24 UTC 
After upgrading from 6.1 to 6.2 some customers experience poor performance due to left over qpid data. Currently they can clear it out via this routine:

 https://access.redhat.com/solutions/2608341

but we should bake this into the --upgrade steps to ensure users never have to experience the performance problem in the first place.
Comment 2 Chris Roberts 2016-10-11 15:23:10 UTC 
added upstream redmine issue

http://projects.theforeman.org/issues/16863
Comment 4 Chris Roberts 2016-11-02 10:12:09 UTC 
*** Bug 1375659 has been marked as a duplicate of this bug. ***
Comment 5 Peter Ondrejka 2016-12-01 14:10:03 UTC 
Verified in 6.2.5

Before upgrade:
 ~]# qpid-config --ssl-certificate=/etc/pki/katello/qpid_client_striped.crt -b amqps://localhost:5671 add queue $(hostname -f):event --force

After upgrade:
 ~]# qpid-stat -q --ssl-certificate=/etc/pki/katello/qpid_client_striped.crt -b amqps://localhost:5671 | grep :event | wc -l
0
Comment 6 errata-xmlrpc 2016-12-12 17:14:13 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-2016:2940