Bug 2047974 - rpm -V / --verify mentions missing /var/run/sanlock
Summary: rpm -V / --verify mentions missing /var/run/sanlock
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: sanlock
Version: 9.0
Hardware: Unspecified
OS: Unspecified
high
medium
Target Milestone: rc
: ---
Assignee: David Teigland
QA Contact: cluster-qe@redhat.com
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-01-28 23:51 UTC by Jiri Jaburek
Modified: 2023-07-28 07:28 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-07-28 07:28:13 UTC
Type: Bug
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHELPLAN-110256 0 None None None 2022-01-28 23:51:49 UTC

Description Jiri Jaburek 2022-01-28 23:51:20 UTC
Description of problem:

After a reboot, rpm verify reports an error:

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

This is likely because the spec file packages it,

%dir %attr(-,sanlock,sanlock) %{_localstatedir}/run/sanlock

however there is no tmpfiles.d entry to re-create it after a reboot, since /var/run is now a symlink to /run, which is a tmpfs, so the packaged directory is gone after a reboot.

Please add a tmpfiles.d entry to make systemd create it on boot, with the right ownership and permissions.

Also consider moving it from the obsolete /var/run to /run, a.k.a. %{_rundir}.


Version-Release number of selected component (if applicable):
sanlock-3.8.4-1.el9

Comment 2 RHEL Program Management 2023-07-28 07:28:13 UTC
After evaluating this issue, there are no plans to address it further or fix it in an upcoming release.  Therefore, it is being closed.  If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.


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