Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
Description of problem:
foreman-rake trends:clean doesn't clean the trend_counters table
Version-Release number of selected component (if applicable):
Satellite 6.1.6
How reproducible:
100%
Steps to Reproduce:
1. Create some trends in satellite 6 either by doing a inserting content into Satellite 6 DB directly
2. Execute the command
# foreman-rake trends:clean ---> command would complete successfully, however it wouldn't stop the linear growth of the trend_counters table in postgres DB
------------------------------------------------------------------------+----------
public.trend_counters | 16 GB
public.index_trend_counters_on_trend_id | 7754 MB
public.trend_counters_pkey | 6016 MB
foreman=# select count(*) from trend_counters;
count
-----------
288490382
(1 row)
# time foreman-rake trends:counter
real 56m5.516s
user 28m10.714s
sys 0m33.396s
Actual results:
trend_counters table is filling up very fast, with huge number of records in it
Expected results:
trends:clean script should actually clean the old data to save up the disk space
Additional info:
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHBA-2016:1500
Description of problem: foreman-rake trends:clean doesn't clean the trend_counters table Version-Release number of selected component (if applicable): Satellite 6.1.6 How reproducible: 100% Steps to Reproduce: 1. Create some trends in satellite 6 either by doing a inserting content into Satellite 6 DB directly 2. Execute the command # foreman-rake trends:clean ---> command would complete successfully, however it wouldn't stop the linear growth of the trend_counters table in postgres DB ------------------------------------------------------------------------+---------- public.trend_counters | 16 GB public.index_trend_counters_on_trend_id | 7754 MB public.trend_counters_pkey | 6016 MB foreman=# select count(*) from trend_counters; count ----------- 288490382 (1 row) # time foreman-rake trends:counter real 56m5.516s user 28m10.714s sys 0m33.396s Actual results: trend_counters table is filling up very fast, with huge number of records in it Expected results: trends:clean script should actually clean the old data to save up the disk space Additional info: