Bug 2047955 - rpm -V / --verify mentions wrong user/mtime for /var/run/opendnssec
Summary: rpm -V / --verify mentions wrong user/mtime for /var/run/opendnssec
Keywords:
Status: NEW
Alias: None
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: opendnssec
Version: 9.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Rafael Jeffman
QA Contact: ipa-qe
URL:
Whiteboard:
Depends On:
Blocks: 2231075
TreeView+ depends on / blocked
 
Reported: 2022-01-28 23:18 UTC by Jiri Jaburek
Modified: 2023-08-10 13:31 UTC (History)
0 users

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 2231075 (view as bug list)
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 FREEIPA-7749 0 None None None 2022-01-28 23:22:54 UTC
Red Hat Issue Tracker RHELPLAN-110250 0 None None None 2022-01-28 23:22:59 UTC

Description Jiri Jaburek 2022-01-28 23:18:48 UTC
Description of problem:

After installing opendnssec, I can see rpm verify showing

# rpm -V opendnssec
.M...U...    /var/run/opendnssec

This is probably because the spec file mentions

  %attr(0770,root,ods) %dir %{_localstatedir}/run/opendnssec

but the file itself has

# ls -ld /var/run/opendnssec
drwxr-xr-x. 2 ods ods 40 Aug 10 16:51 /var/run/opendnssec

Given that there seems to be a correct entry in tmpfiles.d for the new-style /run,

# cat /usr/lib/tmpfiles.d/opendnssec.conf
D /run/opendnssec 0755 ods ods -

consider *not* packaging the obsolete /var/run directory, or fix its user ownership and mode bits to match tmpfiles.d.


Version-Release number of selected component (if applicable):
opendnssec-2.1.8-4.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.