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.
Bug 2226667 - Repository sync failed with error: Subtask Failed Exception A sub task failed and ActiveRecord::InvalidForeignKey
Summary: Repository sync failed with error: Subtask Failed Exception A sub task faile...
Keywords:
Status: CLOSED DUPLICATE of bug 2224031
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Repositories
Version: 6.14.0
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: 6.14.0
Assignee: satellite6-bugs
QA Contact: Satellite QE Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-07-26 07:29 UTC by Amit Agarwal
Modified: 2023-08-11 12:02 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-08-11 12:02:56 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker SAT-19486 0 None None None 2023-08-10 14:14:36 UTC

Description Amit Agarwal 2023-07-26 07:29:36 UTC 
Description of the problem:

I have enabled the following repositories and initiated a product content advanced sync:

Red Hat Enterprise Linux 8 for x86_64 - AppStream RPMs 8

Red Hat Enterprise Linux 8 for x86_64 - BaseOS RPMs 8

Red Hat Enterprise Linux 9 for x86_64 - AppStream RPMs 9

Red Hat Enterprise Linux 9 for x86_64 - BaseOS RPMs 9

Red Hat Satellite Client 6 for RHEL 8 x86_64 RPMs

Red Hat Satellite Client 6 for RHEL 9 x86_64 RPMs

However,'Synchronize: Skip Metadata Check synchronize: skip metadata check; repository 'Red Hat Satellite Client 6 for RHEL 9 x86_64 RPMs'; product 'Red Hat Enterprise Linux for x86_64 shows with the following error message: 

~~
Dynflow::Action::WithSubPlans::SubtaskFailedException

A sub task failed
~~~


Further doing with detailed Dynflow steps repository "Synchronize: Skip Metadata Check repository 'Red Hat Enterprise Linux 9 for x86_64 - AppStream RPMs 9'; product 'Red Hat Enterprise Linux for x86_64'; organization 'RedHat' sync got failed" with below error message -->


Error:

PG::ForeignKeyViolation: ERROR:  insert or update on table "katello_repository_rpms" violates foreign key constraint "fk_rails_39a260fd51"
DETAIL:  Key (rpm_id)=(66914) is not present in table "katello_rpms"..


Re-synchronizing 'Red Hat Enterprise Linux 9 for x86_64 - AppStream RPMs 9'' did resolved the issue.
Comment 1 Ashish Humbe 2023-07-27 04:35:14 UTC 
Looks like this is a duplicate of https://bugzilla.redhat.com/show_bug.cgi?id=2224031
Comment 7 Brad Buckingham 2023-08-11 12:02:56 UTC 
Amit,  

Thanks for retesting this on the latest snap.  Based upon the feedback, I am going to proceed with closing this one as a duplicate of bug 2224031 mentioned in comment 1.   If there are any concerns, please feel free to reopen with appropriate details.

*** This bug has been marked as a duplicate of bug 2224031 ***
Note You need to log in before you can comment on or make changes to this bug.