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:
When setting up a content view and applying a filter that only applies to particular repositories, everything goes fine until you delete the repositories that the filter is applied to. In the absence of any filters, Satellite assumes that you want the filter to apply to all repositories as opposed to leaving the filter as applying to no repositories.


Version-Release number of selected component (if applicable):
6.11.4

How reproducible:
everytime

Steps to Reproduce:
create a CV and create a filter to apply on a single repo from the CV. 
Publish the CV
Now, remove the repo on which the filter was applied, it assumes that the filter is to be applied on all remaining repositories. 

Actual results:
Filter applied to all repos. it has been changed to "Apply to all repositories in the CV" from "Apply to subset of repositories"

Expected results:
No filter should be applied 

Additional info:

This happens through CLI as well as Web UI and tested in 6.11 only.

Created redmine issue https://projects.theforeman.org/issues/36577 from this bug

Moving this bug to POST for triage into Satellite since the upstream issue https://projects.theforeman.org/issues/36577 has been resolved.

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.15.0 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-2024:2010

The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days