+++ This bug was initially created as a clone of Bug #1127298 +++

Description of problem:

Syncing a repo that has lots of missing rpms such as:

http://japan.proximity.on.ca/kojifiles/repos/f20-build/latest/armv6hl/

(which is missing all 30,000 of its rpms) results in a sync that can't be cancelled and workers that cant be restarted.

Cancelling the task seems to do nothing, and restarting the pulp_workers shuts down all but one worker and then hangs waiting for the last worker to die.

Version-Release number of selected component (if applicable):

2.4.0-0.29

How reproducible:
Always

Steps to Reproduce:
1.  Create a repo with this feed  http://japan.proximity.on.ca/kojifiles/repos/f20-build/latest/armv6hl/
2.  Initiate the sync of the repo
3.  Attempt to cancel the repo
4.  attempt to restart pulp_workers

Actual results:

Task cannot be cancelled.  
Restarting pulp_workers hang when trying to shut down one of the workers


Expected results:

Task can be cancelled, pulp_worker restarts fine

--- Additional comment from Barnaby Court on 2014-08-12 15:32:35 EDT ---

This appears to be working with the 2.4 release, there is an extended delay after the task has been marked as canceled where we are still waiting for the worker to die.  Eventually the log file is showing a traceback for a CancelException (used internally by the pulp_rpm sync code when a cancel occurs) and things restart properly.  The delay was on the order of 1-2 minutes.

--- Additional comment from Barnaby Court on 2014-08-14 15:36:02 EDT ---

I did find an issue after the rpms start downloading.  The linked PR is for that item.  After it was fixed I have been unable to get the cancel to hang.  

PR: https://github.com/pulp/pulp_rpm/pull/545