This bug has been migrated to another issue tracking site. It has been closed here and may no longer be being monitored.

If you would like to get updates for this issue, or to participate in it, you may do so at Red Hat Issue Tracker .
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.
Bug 2014061 - [RFE] Need of cleanup task in Satellite to clean openscap reports.
Summary: [RFE] Need of cleanup task in Satellite to clean openscap reports.
Keywords:
Status: CLOSED MIGRATED
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: SCAP Plugin
Version: 6.9.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: Jameer Pathan
URL:
Whiteboard:
: 2196923 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-10-14 12:01 UTC by Akshay Kapse
Modified: 2024-06-06 01:05 UTC (History)
11 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2024-06-06 01:05:49 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker   SAT-5476 0 None Migrated None 2024-06-06 01:05:48 UTC
Red Hat Knowledge Base (Solution) 3040861 0 None None None 2023-05-03 13:01:39 UTC

Description Akshay Kapse 2021-10-14 12:01:48 UTC 
Description of problem:

1. Proposed title of this feature request

- Need of configurable cleanup task in Satellite to clean foreman-openscap reports.

2. Who is the customer behind the request?

Account name: Bundesanstalt für Landwirtschaft und Ernährung (#1573957)
CSM customer: no
TAM customer: no
Strategic Customer: no

3. What is the nature and description of the request?

- The scanning of hosts is done on weekly basis, so the reports generated by this task are consuming storage quickly.
- So, need a configurable recurrent Task in the Satellite Task-System (like the ones already there for disk space notification or rss notifications) to remove the SCAP-reports/logs from the filesystem and from from the Satellite-Database.

4. Why does the customer need this? (List the business requirements here)

- Scap reports are consuming too much space on the Satellite server causing disk to get utilized 100%.
- To avoid the disks getting 100% filled by logs/reports and Satellite functioning get compromised which can affect daily operations.

5. How would the customer like to achieve this? (List the functional requirements here)
- A configurable recurrent task is cleaning up old reports from the Satellite based on 'threshold value of disk utilization' or 'cleaning up 30 days old reports' automatically from Satellite.


Additional info:
- Shared API to cleanup scap reports: https://access.redhat.com/solutions/3040861, but customer mentioned "I expect the product to contain such a functionality out of the box"/"Make it easier".
Comment 1 Marek Hulan 2021-10-15 11:25:12 UTC 
There is already a rake task that cleans up reports of a given type that can easily be called from cron (like with config reports).

foreman-rake reports:expire report_type=ForemanOpenscap::ArfReport

you can also specify days after which reports should be cleaned up

foreman-rake reports:expire report_type=ForemanOpenscap::ArfReport days=7

This isn't configured by default because some customers may need to keep the compliance report for audit purposes. However we plan to move all rake tasks that should be performed regularly to the tasking system and make them easily configurable through settings. At that point, we should add this task there and make it easy to tweak the clean up interval. This is not yet aligned to a specific version though.
Comment 8 visawant 2023-06-21 07:24:44 UTC 
*** Bug 2196923 has been marked as a duplicate of this bug. ***
Comment 9 Brad Buckingham 2023-10-30 11:29:29 UTC 
Bulk setting Target Milestone = 6.15.0 where sat-6.15.0+ is set.
Comment 14 Eric Helms 2024-06-06 01:05:49 UTC 
This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "SAT-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.
Note You need to log in before you can comment on or make changes to this bug.