Hide Forgot
Description of problem: When we cancel a sync associated threads will not exit immediately and finishes the fetch its performing before relinquishing the thread. This is ok for smallers packages/files. But in File Sync case we can have an iso with 4G+ data thats being fetched and the sync will wait for the whole 4G to download before exiting. This might defeat the point of cancel in an iso case as we might not want those G's down. Would it make sense to have an option to kill the process immediately vs being polite.
Commits Below: http://git.fedorahosted.org/git/?p=pulp.git;a=commitdiff;h=ae7289b1d5bbbd36a71a0c35df1547396ad31c96 http://git.fedorahosted.org/git/?p=pulp.git;a=commitdiff;h=613d8cad672196505baa3805ef1f52362490f430 QE: Good test case would be to limit the bandwidth of a repo sync to something really low like 1kb. Then when syncing a repo it should take a long time to fetch packages. When you are ready to test the cancel, issue a 'cancel_sync', you will see a delay of a few seconds as the request is sent to pulp-server and is acted upon. I would expect to see the actual sync canceled within a few seconds of this.
build: 0.222
verified [root@preethi ~]# pulp-admin repo sync --id=f15 --limit=1 -F Sync for repository f15 started Sync: Cancelled Item Details: Tree_Files: 0/6 Rpms: 654/2935 root@preethi ~]# pulp-admin repo cancel_sync --id=f15 Sync for repository f15 is being cancel
Pulp v1.0 is released Closed Current Release.