Bug 654398 - spacewalk-repo-sync - 'could not find object...' messages
Summary: spacewalk-repo-sync - 'could not find object...' messages
Keywords:
Status: CLOSED DUPLICATE of bug 658422
Alias: None
Product: Red Hat Satellite 5
Classification: Red Hat
Component: Satellite Synchronization
Version: 540
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
Assignee: Miroslav Suchý
QA Contact: Red Hat Satellite QA List
URL:
Whiteboard:
Depends On:
Blocks: 462714
TreeView+ depends on / blocked
 
Reported: 2010-11-17 18:56 UTC by Jiri Kastner
Modified: 2018-11-14 14:55 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-02-09 17:11:41 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Jiri Kastner 2010-11-17 18:56:06 UTC
Description of problem:
when i was syncing epel6-beta (not yet released epel6) repo, i noticed 'wall-paper' of 'Could not find object...' messages, not saying, what exactly is going wrong. a more comprehensible message could replace this one.

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

How reproducible:


Steps to Reproduce:
1. install satellite 5.4
2. sync rhel6 channel
3. create repository for rhel6 beta epel
4. create rhel6 sub channel with this repo and sha256 checksum
5. run 'sync now'
6. check results

  
Actual results:
after package download in repolog appear lot of following messages:

Could not find object [<server.importlib.importLib.IncompletePackage instance; attributes={'package_size': None, 'package_arch_id': 104, 'name': 'directfb-devel', 'checksum_list': None, 'md5sum': None, 'org_id': '1', 'package_id': None, 'checksums': {None: None}, 'channels': {232: 'epel-6-i386'}, 'nevra_id': 59378, 'epoch': '', 'version': '1.4.2', 'name_id': 11403, 'last_modified': None, 'checksum': None, 'release': '3.el6', 'checksum_type': None, 'arch': 'i686', 'evr_id': 11450, 'checksum_id': None}] in table rhnPackage

Expected results:
more human readable message

Additional info:

Comment 1 Jiri Kastner 2010-11-18 11:46:14 UTC
i just found, that this also occurs when i have two channels with same repo or two repos with same packages and repodata.

Comment 5 Clifford Perry 2011-02-09 17:11:41 UTC
Based on comment #4 - closing dupe

*** This bug has been marked as a duplicate of bug 658422 ***


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