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.

Bug 2221835

Summary: The command "foreman-rake reports:expire report_type=ForemanOpenscap::ArfReport" does not cleanup the SCAP reports from the Capsule server
Product: Red Hat Satellite Reporter: Jayant Bhatia <jbhatia>
Component: SCAP PluginAssignee: satellite6-bugs <satellite6-bugs>
Status: CLOSED MIGRATED QA Contact: Satellite QE Team <sat-qe-bz-list>
Severity: medium Docs Contact:
Priority: medium    
Version: 6.11.0CC: ahumbe, ehelms, gtalreja, mhulan, nalfassi, sadas, shwsingh
Target Milestone: UnspecifiedKeywords: MigratedToJIRA, Triaged
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2024-06-06 16:24:01 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:
Embargoed:

Description Jayant Bhatia 2023-07-11 01:18:15 UTC
Description of problem:

The command "foreman-rake reports:expire report_type=ForemanOpenscap::ArfReport" only cleans the Openscap report files from Satellite and not from Capsule.

Version-Release number of selected component (if applicable): Satellite-6.14 and below


How reproducible: Always


Steps to Reproduce:
1. Ensure OpenScap is configured and there are reports generated on both Satellite and external capsule server.

2. Run the following commands on Satellite to clear the Openscap reports older than 90 days 

       # foreman-rake reports:expire report_type=ForemanOpenscap::ArfReport days=90

Actual results: The OpenSCAP reports listed for the last 90 days on Satellite under compliance reports. The report files on the Capsule server under "/var/lib/foreman-proxy/openscap/reports/arf/" have not cleaned up and the report files > 90 days old are present.  The above command cleaned up the links to the report files in Satellite but did not clean up the report files in the filesystem on the Capsule.


Expected results: The above command should also clean the report files from Capsule along with Satellite.


Additional info: This behavior is observed on all Satellite versions.

Comment 1 Eric Helms 2024-06-06 16:24:01 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.