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:
Pending tasks do not resume or cancel when doing the force unlock.
How reproducible:
Steps to Reproduce:
1. sync a repo
2. stop pulp_worker service
3. tasks shows up as incomplete
4. try to force unlock the task and resume, task just sits there.
Actual results:
Tasks hangs at pending and when doing the force unlock/resume it just sits there, hammer tasks only gives options to see the status of a task.
Expected results:
Tasks to finish, or a button to kill the tasks from the db
Additional info:
unable to kill tasks with hammer cli, pulp-admin tool does not do anything
Comment 1RHEL Program Management
2014-09-19 22:43:11 UTC
Since this issue was entered in Red Hat Bugzilla, the release flag has been
set to ? to ensure that it is properly evaluated for this release.
(In reply to Chris Roberts from comment #0)
> Steps to Reproduce:
> 1. sync a repo
> 2. stop pulp_worker service
<xixi> "2. stop pulp_worker service"
<xixi> why stop the service?
<xixi> not seeing a restart either
<Toledo> we were trying to reproduce the issue, most of this is happening in the cases when a cu does not have proxy setup correctly and then the jobs get stuck
<Toledo> so even after putting the proxy info in, or if they have networking issues the jobs are still pending
[snip]
> Additional info:
> unable to kill tasks with hammer cli, pulp-admin tool does not do anything
<Toledo> http://projects.theforeman.org/issues/5718