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:
The openscap report files are not removed from the disk when the clean up command is executed.
Version-Release number of selected component (if applicable): 6.12, 6.11, 6.10
How reproducible:
Always
Steps to Reproduce:
1. Run 'foreman-rake reports:expire days=7 report_type=ForemanOpenscap::ArfReport'
Actual results:
the reports are removed from web UI and DB, but the files remain in /var/lib/foreman-proxy/openscap/reports/arf
Expected results:
The corresponding reports in /var/lib/foreman-proxy/openscap/reports/arf should get removed
Additional info:
Tested with Sat v6.12, v6.11 (RHEL8), and v6.10 (RHEL7) and exhibits the same behaviors.
Here is the testing result from v6.12, v.6.11 (RHEL8) and v6.10 (RHEL7)
Reports does not exist:
[root@ito-sat2 ~]# ls -l /var/lib/foreman-proxy/openscap/reports/arf
ls: cannot access '/var/lib/foreman-proxy/openscap/reports/arf': No such file or directory
Ran the openscap on the content host and upload it to the Satellite:
[root@ito-vm1 ~]# /usr/bin/foreman_scap_client 1
Now the file shows up on the satellite:
[root@ito-sat2 ~]# ls -l /var/lib/foreman-proxy/openscap/reports/arf
total 0
drwxr-xr-x. 3 foreman-proxy foreman-proxy 15 May 10 12:24 794d7c3b-7f89-4b1b-a114-ba5add643730
Check how many entries in the DB:
[root@ito-sat2 ~]# su - postgres -c "psql foreman -c \"select to_char(count(*), 'FM9,999,999,999') as logscount from logs;\""
logscount
-----------
310
(1 row)
Running 'foreman-rake reports:expire' command and it will decrease the entries in the DB:
[root@ito-sat2 ~]# /usr/sbin/foreman-rake reports:expire days=0 report_type=ForemanOpenscap::ArfReport
[root@ito-sat2 ~]# su - postgres -c "psql foreman -c \"select to_char(count(*), 'FM9,999,999,999') as logscount from logs;\""
logscount
-----------
38
(1 row)
The reports is removed from the Web UI, but not from the disk.
[root@ito-sat2 ~]# ls -l /var/lib/foreman-proxy/openscap/reports/arf
total 0
drwxr-xr-x. 3 foreman-proxy foreman-proxy 15 May 10 12:24 794d7c3b-7f89-4b1b-a114-ba5add643730
[root@ito-sat2 ~]#