Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

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"

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.