Bug 2159706

Summary: Filter gets applied to all the repository upon removal of repository for which the filter was created.
Product: Red Hat Satellite Reporter: Vedashree Deshpande <vdeshpan>
Component: Content ViewsAssignee: satellite6-bugs <satellite6-bugs>
Status: POST --- QA Contact: Satellite QE Team <sat-qe-bz-list>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 6.11.4CC: ahumbe, iballou, sajha
Target Milestone: UnspecifiedKeywords: Triaged
Target Release: Unused   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Vedashree Deshpande 2023-01-10 12:44:04 UTC 
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:
Comment 3 Vedashree Deshpande 2023-04-03 06:27:56 UTC 
This happens through CLI as well as Web UI and tested in 6.11 only.
Comment 4 Samir Jha 2023-07-10 16:32:43 UTC 
Created redmine issue https://projects.theforeman.org/issues/36577 from this bug
Comment 5 Bryan Kearney 2023-07-19 16:02:40 UTC 
Moving this bug to POST for triage into Satellite since the upstream issue https://projects.theforeman.org/issues/36577 has been resolved.