Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
Description of problem: Capsule sync failed with "no record found error"(ActiveRecord::RecordNotFound: Couldn't find Katello::Repository with 'id').
Version-Release number of selected component (if applicable):
6.9 Snap7
How reproducible:
always
Steps to Reproduce:
1. Spin-up Satellite and Capsules base version 6.8.
2. Upgrade satellite from 6.8 to 6.9 and it completes successfully.
3. Keep Capsule on the base version 6.8(N-1 upgrade)
4. Perform Capsule Optimized Sync and it gets failed with an error
Couldn't find Katello::Repository with 'id'=25Couldn't find Katello::Repository with 'id'=3
Actual results:
Capsule sync failed with no record found error.
Expected results:
Capsule sync should be completed successfully.
Additional info:
Setup:
1) Sat 6.9.0 snap 9 upgraded from 6.8.3 snap 1
2) Caps 6.8.3 snap 1 registered to the Sat above (N-1 setup)
Steps:
1) Synchronized a Puppet CV to the empty capsule - sync succeeded, no history record created
2) Created other content types (yum, file), added to new CV and synced to the capsule - sync succeeded, history record added
3) Removed Puppet CV, resynced, removed yum/file CV, resynced - all succeeded
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory (Moderate: Satellite 6.9 Release), and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHSA-2021:1313