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.
Bug 1805728 - [RHEL8/Bug] abrt rpm verify failed on /var/run/abrt missing after reboot
Summary: [RHEL8/Bug] abrt rpm verify failed on /var/run/abrt missing after reboot
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: abrt
Version: 8.1
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: 8.0
Assignee: abrt
QA Contact: BaseOS QE - Apps
URL:
Whiteboard:
Depends On:
Blocks: 1122832 1819712
TreeView+ depends on / blocked
 
Reported: 2020-02-21 12:52 UTC by Oliver Falk
Modified: 2023-12-15 17:23 UTC (History)
2 users (show)

Fixed In Version: abrt-2.10.9-12.el8
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-11-04 01:31:18 UTC
Type: Bug
Target Upstream Version:
Embargoed:
pm-rhel: mirror+


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2020:4435 0 None None None 2020-11-04 01:31:47 UTC

Description Oliver Falk 2020-02-21 12:52:46 UTC
Description of problem:
abrt rpm installs dirs/files in /var/run/, however since /var/run is symlinked /run and /run is actually on tmpfs in default installs, that means an rpm verify will fail on /var/run/abrt if the machine is rebooted and abrtd isn't enabled to start upon boot.

Version-Release number of selected component (if applicable): 2.10.9


How reproducible: Always


Steps to Reproduce:
1. # yum -y install abrt
2. # systemctl disable abrtd.service
2. # reboot
3. # rpm -V abrt

Actual results:

# rpm -V abrt
missing     /var/run/abrt

Expected results:
RPM verify should not report missing /var/run/abrt.


Additional info:
It's important to note that abrtd shall not start upon reboot, since it will create those entries.

I guess, %ghost in the %files section of the RPM spec file should help, but I'M too low on time to actually give this a try.

Customer case will be linked.

Comment 1 ekulik 2020-02-24 08:48:10 UTC
%ghost seems to do it for me.

Comment 3 ekulik 2020-02-25 09:54:22 UTC
Upstream PR: https://github.com/abrt/abrt/pull/1454

Comment 4 ekulik 2020-02-26 14:42:19 UTC
Martin, can you take a look? This should be a walk in the park to verify.

Comment 5 Martin Kyral 2020-03-02 10:36:56 UTC
Easy to test -> qa_ack+

Comment 12 errata-xmlrpc 2020-11-04 01:31:18 UTC
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 (abrt bug fix and enhancement update), 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-2020:4435


Note You need to log in before you can comment on or make changes to this bug.