Bug 749902 - Grinder Lockfile not cleaned up from a canceled sync
Summary: Grinder Lockfile not cleaned up from a canceled sync
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Pulp
Classification: Retired
Component: user-experience
Version: unspecified
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: Pradeep Kilambi
QA Contact: Preethi Thomas
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-10-28 20:07 UTC by John Matthews
Modified: 2013-09-09 16:33 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-02-24 20:11:14 UTC

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description John Matthews 2011-10-28 20:07:48 UTC 
Description of problem:

If you cancel a sync, the files currently be downloaded while cancelled will not be re-downloaded.

Subsequent invocations of sync result in grinder skipping the actual download.


To reproduce:
1) Sync a repo
2) While downloading, issue a cancel_sync
3) Attempt to resync
 Notice how quick it completes and the files interrupted are not actually downloaded.

Example is what I see:
# ls /var/lib/pulp/packages/pulp-large_10mb_test-package/0.1.1/1.fc15/noarch/d2b/pulp-large_10mb_test-package-0.1.1-1.fc15.noarch.rpm.*
/var/lib/pulp/packages/pulp-large_10mb_test-package/0.1.1/1.fc15/noarch/d2b/pulp-large_10mb_test-package-0.1.1-1.fc15.noarch.rpm.lock
/var/lib/pulp/packages/pulp-large_10mb_test-package/0.1.1/1.fc15/noarch/d2b/pulp-large_10mb_test-package-0.1.1-1.fc15.noarch.rpm.part


I've seen this for rpm syncs and file syncs.
Comment 1 Pradeep Kilambi 2011-10-31 15:09:29 UTC 
fixed! commit da4ea6bb58d72c1a7509ad946e9371482395a620
Comment 2 Jay Dobies 2011-11-09 20:32:12 UTC 
Fixed in build 0.247.
Comment 3 Preethi Thomas 2011-12-08 20:07:35 UTC 
verified
[root@preethi ~]# rpm -q pulp
pulp-0.0.254-2.fc15.noarch
Comment 4 Preethi Thomas 2012-02-24 20:11:14 UTC 
Pulp v1.0 is released
Closed Current Release.
Note You need to log in before you can comment on or make changes to this bug.