Bug 1394358
Summary: | [upgrades] Clear out qpid event queue upon upgrade | ||
---|---|---|---|
Product: | Red Hat Satellite | Reporter: | Bryan Kearney <bkearney> |
Component: | Upgrades | Assignee: | satellite6-bugs <satellite6-bugs> |
Status: | CLOSED ERRATA | QA Contact: | Jitendra Yejare <jyejare> |
Severity: | high | Docs Contact: | |
Priority: | high | ||
Version: | 6.2.0 | CC: | bbuckingham, bkearney, chrobert, cwelton, ehelms, inecas, jcallaha, mbacovsk, mmccune, pmoravec |
Target Milestone: | Unspecified | Keywords: | PrioBumpField, Triaged |
Target Release: | Unused | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
URL: | http://projects.theforeman.org/issues/16863 | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | 1382524 | Environment: | |
Last Closed: | 2018-02-21 16:54:37 UTC | Type: | --- |
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: | 1382524 | ||
Bug Blocks: |
Comment 2
Bryan Kearney
2016-11-11 21:12:07 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. 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
|