Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
It has been noticed in several cases that upgrade from 6.1.9 to 6.2 removed gutterball bits (thats ok) but did not remove its queue $(fqdn):event in qpid broker.
Since candlepin sends events to that queue even in 6.2, the queue gets full after some time, causing candlepin either slowed down or raising errors (I can explain why if interested). That has severe impact to whole Satellite, like performance down, or even WebUI returning 503 (passenger serves only rhsm/candlepin requests until they timeout).
The upgrade has to delete the queue in either way. It is safe for candlepin, since candlepin sends the events to a qpid exchange that routes the messages to the queue - candlepin itself does not know about presence of the queue at all.
Version-Release number of selected component (if applicable):
Sat 6.2
How reproducible:
??? (maybe 100%)
Steps to Reproduce:
1. Install Sat6.1.9
2. Upgrade to 6.2
3. qpid-stat -q --ssl-certificate=/etc/pki/katello/qpid_client_striped.crt -b amqps://localhost:5671 | grep :event
Actual results:
3. returns:
pmoravec-sat61-rhel7.gsslab.brq.redhat.com:event Y 81 81 0 6.93m 6.93m 0 0 2
And the counters (81 in above example) are rising over the time (just trigger some candlepin work for that)
Expected results:
3. returns nothing
Additional info: