Bug #17777
open
Should be easy to find out which packages failed to download during a content sync
Description
Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=1261632
Description of problem:
I synced RHEL 6 Server RPMs, which was almost 30gb of content, but was told 4 hours later that 4 packages failed to download. The sync said it was complete on Sync Status, and the task info for it also reported success. Trying to figure out which 4 packages I was missing, and hoping they weren't important, I tried to find out what they were. I didn't see them on Content Sync, the Task details screen, or in the Errors tab of that Task (which said there were "No errors").
After giving up and asking a dev for help, I was told to look in the Raw tab and scan the JSON for the packages. Sure enough, under Yum Importer, Error Details, there were 4 packages listed, all with "Connection aborted", BadStatusLine(\"''\",).
It looks like there's currently a bug for sync errors reporting as fine, so this may fall under that until it gets fixed, but it would be nice if we exposed the packages that had issues downloading in a more findable fashion. I'd expect to either see them on the Task details under Output, or in the Errors tab for the sync task, it seems like important information to me.
Actual results:
"Failed to download 4 packages." Ok, which ones?
Expected results:
"Failed to download 4 packages: package-x, package-y, package-z, package-z++."
Additional info:
When a failure happens, at what point will they try to download again?
Updated by Brad Buckingham over 7 years ago
- Subject changed from Should be easy to find out which packages failed to download during a content sync to Should be easy to find out which packages failed to download during a content sync
- translation missing: en.field_release set to 114