Red Hat Bugzilla – Bug 1098264
Syncing yum repo does not decrement size_left or items_left within task if packages have already been synced in another repo
Last modified: 2014-08-19 23:31:51 EDT
Created attachment 895993 [details]
Description of problem:
Currently sync tasks do not seem to be incrementing size_left, items_left, or rpm_done.
This occurs both in the progress report and the 'result'
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Create a yum repo with a feed url
2. Sync the repo
3. Examine the sync task (pulp-admin tasks details --task-id=b16f4fe9-1343-468c-a6f9-3a356a003368)
size_left, items_left, and rpm_done
size_left, items_left, and rpm_done should all decrement as the sync progresses and should be 0 (assuming it did not error)
Attached full task object
Hrmmm, this may be a little more odd than i thought. Syncing a new repo the sync seems to just be complete randomly before it is done. See:
In this case the task was complete (in fact it went on to publish the distributors), but there were no errors.
but note in the scenario of comment #1, all 3480 packages did actually sync. Looking at the repo's packages afterwards seems to indicate that.
Ahh, I think i've figured this out. If the package has already been synced, it and thus the packages do not need to be imported the rom_done count and size_left count will not decrement.
So the reproduction steps should be:
1. Create Repo A with a feed URL
2. Sync Repo A
3. Create Repo B with the SAME feed URL
4. Sync Repo B
Result: Repo B's counts will not be decremented.
This is a dup of https://bugzilla.redhat.com/show_bug.cgi?id=1095332 and I am already close to fixing it. Basically when we remove packages which are already downloaded from the to_be_downloaded list, we were not updating the progress for new number and size of packages. That is why the size and number of packages are reducing for the packages getting downloaded but do not reach zero at the end.
Meant to close it as a dup, not NOTABUG.
*** This bug has been marked as a duplicate of bug 1095332 ***