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.
Bug 1144621 - Satellite 6: Pending Pulp actions cannot cancel (such as when jobs get stuck or any network issues while jobs are pending)
Summary: Satellite 6: Pending Pulp actions cannot cancel (such as when jobs get stuck ...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Content Management
Version: Unspecified
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: Unspecified
Assignee: Brad Buckingham
QA Contact: Tazim Kolhar
URL:
Whiteboard:
Depends On: 1145724
Blocks: sat6-pulp-future GSS_Sat6Beta_Tracker, GSS_Sat6_Tracker
TreeView+ depends on / blocked
 
Reported: 2014-09-19 22:37 UTC by Chris Roberts
Modified: 2019-10-10 09:24 UTC (History)
11 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
: 1145724 (view as bug list)
Environment:
Last Closed: 2015-08-12 13:58:31 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Chris Roberts 2014-09-19 22:37:41 UTC 
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 1 RHEL 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.
Comment 3 Xixi 2014-09-19 22:47:05 UTC 
(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
Comment 9 Michael Hrivnak 2015-01-19 14:36:58 UTC 
I closed the upstream bug since it seems this issue is sufficiently resolved. Please re-open it if there are any additional changes you want to see.
Comment 11 Tazim Kolhar 2015-05-19 08:48:23 UTC 
VERIFIED:

# rpm -qa | grep foreman
foreman-1.7.2.21-1.el7sat.noarch
ruby193-rubygem-foreman_discovery-2.0.0.13-1.el7sat.noarch
foreman-libvirt-1.7.2.21-1.el7sat.noarch
ruby193-rubygem-foreman_gutterball-0.0.1.9-1.el7sat.noarch
foreman-postgresql-1.7.2.21-1.el7sat.noarch
ruby193-rubygem-foreman_bootdisk-4.0.2.13-1.el7sat.noarch
dell-pem710-01.rhts.eng.bos.redhat.com-foreman-proxy-client-1.0-1.noarch
foreman-ovirt-1.7.2.21-1.el7sat.noarch
rubygem-hammer_cli_foreman-0.1.4.11-1.el7sat.noarch
foreman-selinux-1.7.2.13-1.el7sat.noarch
foreman-gce-1.7.2.21-1.el7sat.noarch
ruby193-rubygem-foreman-redhat_access-0.1.0-1.el7sat.noarch
ruby193-rubygem-foreman-tasks-0.6.12.5-1.el7sat.noarch
rubygem-hammer_cli_foreman_tasks-0.0.3.4-1.el7sat.noarch
rubygem-hammer_cli_foreman_docker-0.0.3.6-1.el7sat.noarch
ruby193-rubygem-foreman_docker-1.2.0.12-1.el7sat.noarch
ruby193-rubygem-foreman_hooks-0.3.7-2.el7sat.noarch
rubygem-hammer_cli_foreman_bootdisk-0.1.2.7-1.el7sat.noarch
foreman-proxy-1.7.2.4-1.el7sat.noarch
dell-pem710-01.rhts.eng.bos.redhat.com-foreman-client-1.0-1.noarch
dell-pem710-01.rhts.eng.bos.redhat.com-foreman-proxy-1.0-2.noarch
foreman-vmware-1.7.2.21-1.el7sat.noarch
rubygem-hammer_cli_foreman_discovery-0.0.1.10-1.el7sat.noarch
foreman-compute-1.7.2.21-1.el7sat.noarch
foreman-debug-1.7.2.21-1.el7sat.noarch

steps:
1. sync a repo
2. stop pulp_worker service
3. tasks shows up as incomplete
4. try to force unlock the task and resume
5. task finishes
Comment 12 Bryan Kearney 2015-08-11 13:33:07 UTC 
This bug is slated to be released with Satellite 6.1.
Comment 13 Bryan Kearney 2015-08-12 13:58:31 UTC 
This bug was fixed in version 6.1.1 of Satellite which was released on 12 August, 2015.
Note You need to log in before you can comment on or make changes to this bug.