Bug 1389855

Summary:	Applying filters to satellite-tools repo blocks entire repo from satellite clients
Product:	Red Hat Satellite	Reporter:	John <jrilling>
Component:	Content Views	Assignee:	satellite6-bugs <satellite6-bugs>
Status:	CLOSED NOTABUG	QA Contact:	Bruno Rocha <rochacbruno>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	6.2.2	CC:	bbuckingham, cwelton, mmccune
Target Milestone:	Unspecified
Target Release:	Unused
Hardware:	x86_64
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-11-01 15:07:41 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description John 2016-10-28 23:38:55 UTC

Description of problem:
Applying errata filters on the satellite-tools repo causes all clients to not see the katello-agent which is required for client-satellite communication.
Repeatable everytime!

Many clients have regulatory security errata requirements. In my clients case they asked:
1) to filter ALL bugfix and enhancement errata.
2) Filter last 90 days of security errata for production systems.
Please see case listed at end of ticket for extensive description of filters/troubleshooting.


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

How reproducible:
1. Create a Content View with RHEL6 and satellite-tools repos
2. Apply errata filters to satellite-tools repo
3. On the satellite client run "yum install katello-agent"

Steps to Reproduce:
1. Create a Content View with RHEL6 and satellite-tools repos
2. Apply errata filters to satellite-tools repo
3. On the satellite client run "yum install katello-agent"

Actual results:
katello-agent package not found, nothing to do

Expected results:
installing katello-agent

Additional info:
The case below provides extensive detail regarding this issue:
https://access.redhat.com/support/cases/#/case/01728014

Comment 1 Mike McCune 2016-11-01 15:07:41 UTC

This really isn't a bug as the user put a filter on the Satellite Tools repository that indicated they wanted all errata from 2016 filtered excluded. Since all the content in Satellite Tools 6.2 repository was released as part of errata in 2016 this removes all the packages from the repo.


Copied from the case:

"""
The key to remember is that Errata are just metadata and a collection of packages tied to that metadata. The filters on Errata add and remove the *packages* associated to that errata. 

You in essence are telling the Satellite: "Remove every package from this repository that is associated to these errata I'm filtering out" 

Since every single package in that repository is tied to the errata you filtered out, you end up with 0 packages in the repo because there are no packages that are *not* part of an errata. This isn't a bug, it is doing exactly what you told it to do.
"""

What we need to do is better explain what the filters are doing and indicate to the user that the results of their filters will create 0 package repositories which is not desirable. That would be a different bug/RFE.

Happy to accept an an RFE to better handle this situation around the effects of filters but they are working as designed, even if you can create strange/useless results.