Why do we get "Could not find object" errors when running spacewalk-repo-sync on RHN Satellite v5.4.1?

Solution Verified - Updated -

Environment

  • Red Hat Network Satellite 5.4.1
  • Installed spacewalk-backend package of version >= 1.2.13-75

Issue

  • Errors when running spacewalk-repo-sync for channel linked to external yum repo, like the following:

7/7 : fibreutils-3.2-4-0.x86_64
Could not find object [<server.importlib.importLib.IncompletePackage instance; attributes={'package_size': None, 'package_arch_id': 119, 'name': 'fibreutils', 'checksum_list': None, 'md5sum': None, 'org_id': '45', 'epoch': '', 'checksums': {'md5': '668aaed9c017895da3578b4c96634892'}, 'channels': {1945: 'tpapaioa-00589382-rhel6'}, 'nevra_id': 137349, 'package_id': None, 'last_modified': None, 'name_id': 9555, 'version': '3.2', 'checksum': '668aaed9c017895da3578b4c96634892', 'release': '4', 'checksum_type': 'md5', 'arch': 'x86_64', 'evr_id': 30886, 'checksum_id': 7538339}] in table rhnPackage
  • spacewalk-repo-sync fails to import packages into custom channel
  • satellite-sync results in error "Could not find object [<server.importlib.importLib.IncompletePackage instance; attributes=...] " when trying to sync custom channels under different organization with same repo.

Resolution

  • This issue is fixed in spacewalk-backend-1.2.13-77 version provided by the errata RHBA-2012-1601
  • Follow bellow steps to apply this fix
# yum update spacewalk-backend-1.2.13-77

# rhn-satellite restart

Root Cause

  • spacewalk-repo-sync does not properly handle package record lookup when the same package exists in more than one organization on the Satellite

This solution is part of Red Hat’s fast-track publication program, providing a huge library of solutions that Red Hat engineers have created while supporting our customers. To give you the knowledge you need the instant it becomes available, these articles may be presented in a raw and unedited form.

Comments