| Summary: | foreman-rake trends:clean doesn't clean the trend_counters table | ||
|---|---|---|---|
| Product: | Red Hat Satellite | Reporter: | Nagoor Shaik <nshaik> |
| Component: | Other | Assignee: | Katello Bug Bin <katello-bugs> |
| Status: | CLOSED ERRATA | QA Contact: | Chris Roberts <chrobert> |
| Severity: | medium | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 6.1.6 | CC: | bkearney, chrobert, cwelton, ohadlevy, stkachen |
| Target Milestone: | Unspecified | ||
| Target Release: | Unused | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2016-07-27 09:01:56 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: | |
trends storage has been rewritten in 6.2, setting on QE as this should already be resolved. 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: