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.
In certain situations the user can end up with large lists of this task running or stuck in paused:pending state and can't be mass resumed.
See attached screenshot.
We need to ensure there is only one of these tasks running at a time and we don't spam the tasks list with multiple tasks that can't be mass resumed.
Reproducer steps:
1. Verify no Pending ListenOnCandlepinEvents tasks exist under Monitor > Tasks (or if they do count the # that do)
2. Shut down qpidd
3. Restart foreman-tasks and wait ~60 seconds
4. Restart foreman-tasks again and wait ~60 seconds
5. start qpidd
6. Restart foreman-tasks once more
Result:
Under Monitor > Tasks you will see one or more tasks stuck in 'pending'/.
Verified this bug on latest Satellite GA Snap 14 as per the steps mentioned in comment 3.
The bug is no more reproducible and has been fixed.
Scrrenshot attached.