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:
If you suspend the qpid process (simulating high qpid load), the candlepin event listener process will hang in its event loop. This causes the dynflow executor to not proceed.
For example:
* on tasks page, view candlepin task process, it should say something like:
<pre>
{"messages"=>"b190e333-7821-302a-8131-9693e66e2144",
"last_message"=>"b190e333-7821-302a-8131-9693e66e2144 - import.created",
"error"=>nil,
"connection"=>"Connected"}
</pre>
* now, freeze the qpidd process: kill -19 `pidof qpidd`. Note that the candlepin event listener still thinks its connected.
* do a "hammer ping", it will hang due to https://pulp.plan.io/issues/2253.
* do a "foreman-rake console" and run Katello::Ping.ping(services: [:foreman_tasks]). Note that the executor failed to respond.
Once qpidd is unsuspended via kill -18, things will run normally again.
Version-Release number of selected component (if applicable): 6.2
This is a bug that jhutar originally found a few months ago. What happens is if qpid slows down, the Katello connection to qpid may eventually terminate after minutes/hours but Katello is none the wiser. Qpid will become responsive again, but the katello_event_queue will then keep filling as candlepin puts more events on it.
I have not reproduced this since it can take some time but I believe that is what happened.
The workaround is to restart foreman_tasks if the katello_event_queue appears to not be draining.
Description of problem: If you suspend the qpid process (simulating high qpid load), the candlepin event listener process will hang in its event loop. This causes the dynflow executor to not proceed. For example: * on tasks page, view candlepin task process, it should say something like: <pre> {"messages"=>"b190e333-7821-302a-8131-9693e66e2144", "last_message"=>"b190e333-7821-302a-8131-9693e66e2144 - import.created", "error"=>nil, "connection"=>"Connected"} </pre> * now, freeze the qpidd process: kill -19 `pidof qpidd`. Note that the candlepin event listener still thinks its connected. * do a "hammer ping", it will hang due to https://pulp.plan.io/issues/2253. * do a "foreman-rake console" and run Katello::Ping.ping(services: [:foreman_tasks]). Note that the executor failed to respond. Once qpidd is unsuspended via kill -18, things will run normally again. Version-Release number of selected component (if applicable): 6.2