Bug 1793566

Summary:	[RFE] Fact and report collecting should be opt-in
Product:	Red Hat Satellite	Reporter:	Bryan Kearney <bkearney>
Component:	Fact	Assignee:	satellite6-bugs <satellite6-bugs>
Status:	CLOSED WONTFIX	QA Contact:	Radovan Drazny <rdrazny>
Severity:	high	Docs Contact:
Priority:	high
Version:	6.4	CC:	lzap, mhulan
Target Milestone:	Unspecified	Keywords:	FutureFeature
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:	2020-03-11 14:03:50 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 Bryan Kearney 2020-01-21 15:13:17 UTC

Storing lots of fact and/or report data can quickly go out of control and our research shows that not everyone uses these Foreman features. We would like to make fact and report data storing in Foreman database opt-in via Administer setting. For new installations this will be turned off.

As part of this feature, we will modify "empty" page for Facts and Reports to ask users to enable the setting if they want to start gathering data.

For existing installations, Foreman will either keep collecting data (if there are any) or switch it off by default. It hasn't been decided yet.

Comment 1 Bryan Kearney 2020-01-21 15:13:24 UTC

Created from redmine issue https://projects.theforeman.org/issues/28825

Comment 2 Bryan Kearney 2020-01-21 15:13:29 UTC

Upstream bug assigned to None

Comment 4 Lukas Zapletal 2020-03-11 14:03:50 UTC

The upstream patch was rejected in the form of a simple implementation of a flag that disables facts/reports parsing. Concerns:

 * the patch creates problem for subscription-manager and puppet facts which we parse and store as extra host attributes like uptime or cpu/core count and memory
 * there is now effort to disble or extract puppet code into plugin which will sove the issue
 * we want to have less settings overall to decrease matrix of possible states for easier troubleshooting
 * initial effort and evaluation has been done in order to find better ways to store reports and facts in the DB
 * this is a dirty and temporary solution to the problem, we should really push for cleaner solution no matter how much more work it is

I am going to close this BZ because if we want to solve the problem, we probably need to take a different approach.