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.

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.

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

Upstream bug assigned to None

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.