Bug 800078 - Report synchronization failed when problems with downloading packages (for example due to mismatched checksums
Summary: Report synchronization failed when problems with downloading packages (for ex...
Keywords:
Status: CLOSED DUPLICATE of bug 798683
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Content Management
Version: 6.0.0
Hardware: Unspecified
OS: Unspecified
unspecified
high vote
Target Milestone: Unspecified
Assignee: Katello Bug Bin
QA Contact: Katello QA List
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-03-05 17:25 UTC by Ivan Necas
Modified: 2013-03-27 20:36 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-03-06 08:57:49 UTC
Target Upstream Version:


Attachments (Terms of Use)
response from pulp (4.56 KB, application/json)
2012-03-05 17:25 UTC, Ivan Necas
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 798683 0 medium CLOSED Promoting a product from CLI doesn't promote all product distributions 2021-02-22 00:41:40 UTC

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.


Note You need to log in before you can comment on or make changes to this bug.