Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 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 "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". 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 "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-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:
abrt-vmcore shall remove the vmcore data from /var/crash after harvesting. Currently, it doesn't do so resulting in disk space vasting (the same data are present in /var/spool/abrt):

[root@sheep-41 ~]# ls /var/spool/abrt
vmcore-127.0.0.1-2018-02-16-12:47:16
[root@sheep-41 ~]# ls /var/crash/
127.0.0.1-2018-02-16-12:47:16
[root@sheep-41 ~]#


Version-Release number of selected component (if applicable):
abrt-2.1.11-50.el7

How reproducible:


Steps to Reproduce:
1. have a system with kernel panic gathered by kdump service
2. start abrt-vmcore to harvest the vmocre data
3. ls /var/crash

Actual results:
The vmcore is still there

Expected results:
The vmcore is gone

Additional info:

One AVC still preventing abrt-harvest-core to delete crashes from /var/crash/

type=PROCTITLE msg=audit(1528188455.055:405): proctitle=2F7573722F62696E2F707974686F6E002F7573722F7362696E2F616272742D686172766573742D766D636F7265
type=SYSCALL msg=audit(1528188455.055:405): arch=c000003e syscall=84 success=no exit=-13 a0=27a6980 a1=0 a2=1 a3=0 items=0 ppid=1 pid=5718 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm="abrt-harvest-vm" exe="/usr/bin/python2.7" subj=system_u:system_r:abrt_t:s0-s0:c0.c1023 key=(null)
type=AVC msg=audit(1528188455.055:405): avc: denied { rmdir } for pid=5718 comm="abrt-harvest-vm" name="test2" dev="dm-0" ino=8389095 scontext=system_u:system_r:abrt_t:s0-s0:c0.c1023 tcontext=unconfined_u:object_r:kdump_crash_t:s0 tclass=dir permissive=0

reassigning to Lukáš Vrabec

*** This bug has been marked as a duplicate of bug 1491585 ***