Bug 1912209 - Capsule sync failed with "no record found error"(ActiveRecord::RecordNotFound: Couldn't find Katello::Repository with 'id').
Summary: Capsule sync failed with "no record found error"(ActiveRecord::RecordNotFound...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Capsule - Content
Version: 6.9.0
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: 6.9.0
Assignee: Justin Sherrill
QA Contact: Vladimír Sedmík
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-01-04 05:54 UTC by Devendra Singh
Modified: 2021-04-21 13:25 UTC (History)
1 user (show)

Fixed In Version: tfm-rubygem-katello-3.18.1-1
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-04-21 13:25:01 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 31469 0 Normal Closed smart proxy sync fails with puppet content, leading to paused tasks. 2021-01-19 07:15:59 UTC
Red Hat Product Errata RHSA-2021:1313 0 None None None 2021-04-21 13:25:18 UTC

Description Devendra Singh 2021-01-04 05:54:38 UTC
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:

Comment 2 Justin Sherrill 2021-01-04 17:12:51 UTC
Connecting redmine issue https://projects.theforeman.org/issues/31469 from this bug

Comment 3 Vladimír Sedmík 2021-01-20 09:47:21 UTC
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

Comment 6 errata-xmlrpc 2021-04-21 13:25:01 UTC
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


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