Bug 1846290

Summary:	[RFE] Implement fact whitelist filtering logic
Product:	Red Hat Satellite	Reporter:	Stefan Nemeth <snemeth>
Component:	Fact	Assignee:	satellite6-bugs <satellite6-bugs>
Status:	CLOSED WONTFIX	QA Contact:	Radek Mynar <rmynar>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	6.7.0	CC:	bkearney, ktordeur, mhulan
Target Milestone:	Unspecified	Keywords:	FutureFeature, Triaged
Target Release:	Unused
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2021-08-10 21:37:00 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:
Embargoed:

Description Stefan Nemeth 2020-06-11 10:10:16 UTC

Description of problem:

If there are some hosts with a lot of different asible facts, processing of ansible job can take very long time or even fail with "500 internal server error". There can be a lot of different facts, with different names, so filters blacklist can grow very large. 

To mitigate this, switch to reverse logic, so only specified facts will be stored, can be solution for such deployments.

https://bugzilla.redhat.com/show_bug.cgi?id=1829881

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

6.7.0

How reproducible:

100%


Actual results:

filter can blacklist facts 

Expected results:

have option to reverse filter logic. Switch to whitelist filter instead of blacklist system-wide if needed.

Additional info:

Comment 1 Marek Hulan 2020-06-11 11:27:14 UTC

While the blacklist may be still good default, since users don't know what facts they are interested in in the beginning, after a while, they may want to define whitelist instead to avoid importing useless information. Ideally there's a switch, whether blacklist of whitelist should be used and a setting for each of those options.

Comment 2 Mike McCune 2021-07-13 21:54:48 UTC

Upon review of our valid but aging backlog the Satellite Team has concluded that this Bugzilla does not meet the criteria for a resolution in the near term, and are planning to close in a month. This message may be a repeat of a previous update and the bug is again being considered to be closed. If you have any concerns about this, please contact your Red Hat Account team.  Thank you.

Comment 3 Mike McCune 2021-08-10 21:34:00 UTC

Thank you for your interest in Red Hat Satellite. We have evaluated this request, and while we recognize that it is a valid request, we do not expect this to be implemented in the product in the foreseeable future. This is due to other priorities for the product, and not a reflection on the request itself. We are therefore closing this out as WONTFIX. If you have any concerns about this feel free to contact your Red Hat Account Team. Thank you.