Bug 800078

Summary: Report synchronization failed when problems with downloading packages (for example due to mismatched checksums
Product: Red Hat Satellite Reporter: Ivan Necas <inecas>
Component: Content ManagementAssignee: Katello Bug Bin <katello-bugs>
Status: CLOSED DUPLICATE QA Contact: Katello QA List <katello-qa-list>
Severity: high Docs Contact:
Priority: unspecified    
Version: 6.0.0   
Target Milestone: Unspecified   
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-03-06 08:57:49 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
response from pulp none

Description Ivan Necas 2012-03-05 17:25:45 UTC 
Created attachment 567691 [details]
response from pulp

Description of problem:
it occurs when checksums of files in .treeinfo (or perhaps in medatada) don't correspond to actual checksums of the files.

I've created a fake repo with similar problem here:
http://inecas.fedorapeople.org/fakerepos/ks_invalid . 3 files are not synchronized at all. But Katello reports the result as "Sync complete"

So for temporary workaround update img files to have correct checksums. We need
to figure out how to handle this problems generally: I would expect reporting
synchronization as unsuccessful.

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


How reproducible:


Steps to Reproduce:
1. create product and repo with files with invalid checksums (e.g.http://inecas.fedorapeople.org/fakerepos/ks_invalid)
2. syncrhonize
  
Actual results:
Pulp reports errors (see attachment), but Katello dont.

Expected results:

Katello reports "Sync failed"
Comment 1 Ivan Necas 2012-03-05 17:28:14 UTC 
This leads to unexpected behavior when trying to promote. (e.g. https://bugzilla.redhat.com/show_bug.cgi?id=798683). Without reporting problems in synchronization, it's hard to diagnose this kind of problems.