Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 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 "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". 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 "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-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.

In the KCS here we have common cleanup recommendations:

https://access.redhat.com/solutions/4797161

We unfortunately do not collect the data required to determine if cleanup is required.

We need to add a series of queries and data to every foreman-debug/sosreport:

1) SQL tablesizes: https://github.com/RedHatSatellite/satellite-support/blob/master/postgres-size-report

2) fact_names query:

# su - postgres -c "psql foreman -c \"select name from fact_names;\"" > pg_fact_names.log
# awk -F "::" '{ print $1 }' pg_fact_names.log | sort | uniq -c | sort -nr | head -n5

3) Size of audits, logs and cp_events tables:

su - postgres -c "psql foreman -c \"select count(*) from audits;\"" > audits_table_count.log

su - postgres -c "psql foreman -c \"select count(*) from logs;\"" > logs_table_count.log

su - postgres -c "psql candlepin -c \"select count(*) from cp_event;\"" > cp_event_table_count.log

I realize cp_event is gone in 6.7+ but since sosreport runs on older versions of Satellite there is still value in including this check for our existing 6.6 and prior customers.

Thanks for the feedback. I raised https://github.com/sosreport/sos/pull/2117 in sos upstream.

Some subtle changes:
- limit 100 applied to the fact_names query
- cp_events counts not collected (as this wont be backported to 7.9 due to the progress of the release, hence RHEL8 backport only, hence Sat7 only, where the table is missing)
- I named the files to be written as 'audits_table_count', 'logs_table_count' and 'fact_names_prefixes' - neither sounds me like a great name, I would appreciate if one comes with something better
  - see https://github.com/sosreport/sos/pull/2117/files#diff-9417b117c132fe3ae34b5c209183facfR226-R228

The fix will be delivered in sosreport, hence reassinging to proper product and component.

Mike, could you please verify the fix, once a candidate build available (I guess once for RHEL7.* and then for 8.4, when Sat will be available there)? To grant OtherQE..

After evaluating this issue, there are no plans to address it further or fix it in an upcoming release.  Therefore, it is being closed.  If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.