Bug 1394358 - [upgrades] Clear out qpid event queue upon upgrade
Summary: [upgrades] Clear out qpid event queue upon upgrade
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Upgrades
Version: 6.2.0
Hardware: x86_64
OS: Linux
high
high vote
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: Jitendra Yejare
URL: http://projects.theforeman.org/issues...
Whiteboard:
Depends On: 1382524
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-11-11 19:45 UTC by Bryan Kearney
Modified: 2019-04-01 20:27 UTC (History)
10 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1382524
Environment:
Last Closed: 2018-02-21 16:54:37 UTC
Target Upstream Version:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 16863 0 None None None 2016-11-11 19:45:14 UTC

Comment 2 Bryan Kearney 2016-11-11 21:12:07 UTC
Moving this bug to POST for triage into Satellite 6 since the upstream issue http://projects.theforeman.org/issues/16863 has been resolved.

Comment 3 Jitendra Yejare 2017-12-07 10:25:43 UTC
Verified!

@ Satellite 6.3 Snap 27

The upgrade is performed from 6.2 to latest 6.3 snap 27.

Following Checks are performed for verification of this bug:

1. No QPID queue:
-------------------

# qpid-stat -q --ssl-certificate=/etc/pki/katello/qpid_client_striped.crt -b amqps://localhost:5671 | grep :event | wc -l
0

2. No pending requests against rhsm through passenger status:
-----------------------------------------------------------------

# passenger-status --show=requests
Version : 4.0.18
Date    : 2017-12-07 05:10:57 -0500
Instance: 1744
0 clients:

3. No queue full error log in httpd service:
----------------------------------------------
# # cat /var/log/httpd/error_log | grep -w full | wc -l
0


Hence, I confirm that all the qpid events ques have been cleared during upgrade. And It should have positive effect on performance post upgrade.

Comment 5 Satellite Program 2018-02-21 16:54:37 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-2018:0336


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