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.

Bug 2151333

Summary: Mirror complete sync policy no longer allowed with ignored content types in the repo.
Product: Red Hat Satellite Reporter: Samir Jha <sajha>
Component: RepositoriesAssignee: Samir Jha <sajha>
Status: CLOSED ERRATA QA Contact: Ian Ballou <iballou>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 6.10.0CC: iballou, jbhatia, pcreech, rlavi, saydas, vcojot, visawant
Target Milestone: 6.13.0Keywords: Regression, Triaged
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: rubygem-katello-4.7.0.1 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-05-03 13:23:27 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Samir Jha 2022-12-06 18:34:50 UTC 
https://community.theforeman.org/t/smart-proxy-sync-issue/31479

<pre>
HTTP status code: 400
Response headers: {"date"=>"Tue, 06 Dec 2022 08:46:13 GMT", "server"=>"gunicorn", "content-type"=>"application/json", "vary"=>"Accept,Cookie", "allow"=>"POST, OPTIONS", "x-frame-options"=>"DENY", "content-length"=>"80", "x-content-type-options"=>"nosniff", "referrer-policy"=>"same-origin", "correlation-id"=>"db6665cc-ac06-4170-bb9d-307854ced663", "access-control-expose-headers"=>"Correlation-ID", "via"=>"1.1 ukwdr-foremanp-01.iongroup.net", "connection"=>"close"}
Response body: ["Cannot use 'skip_types' in combination with a 'mirror_complete' sync policy."]
</pre>
Comment 1 Samir Jha 2022-12-06 18:34:53 UTC 
Created from redmine issue https://projects.theforeman.org/issues/35829
Comment 2 Samir Jha 2022-12-06 18:34:55 UTC 
Upstream bug assigned to None
Comment 3 Samir Jha 2022-12-06 18:38:06 UTC 
Proposing this for 6.13 as this impacts all yum repo capsule syncs where Ignore SRPMs is set to true.

Testing steps:

1. Create a repo with Ignore SRPMs checked and Mirroring Policy: Complete mirroring
2. Sync > You should hit the error.
3. If you have a capsule in the environment, try syncing the capsule and you'll see the error for any repos with Ignore SRPMs checked regardless of mirroring policy on the repo.
Comment 4 Bryan Kearney 2022-12-08 00:03:31 UTC 
Moving this bug to POST for triage into Satellite since the upstream issue https://projects.theforeman.org/issues/35829 has been resolved.
Comment 5 Ian Ballou 2023-01-09 22:13:58 UTC 
Verified!

I am no longer able to set the skip types on repositories that have complete mirroring set. I also tried the migration manually to verify that it works.
Comment 8 errata-xmlrpc 2023-05-03 13:23:27 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 (Important: Satellite 6.13 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-2023:2097