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:
The unbound-anchor.timer updates the file /var/lib/systemd/timers/stamp-unbound-anchor.timer, so shouldn't that be noted in /etc/rwtab.d/unbound, for example?

Version-Release number of selected component (if applicable):
unbound-libs-1.4.20-28.el7.x86_64


How reproducible:
Enable unbound and notice that /var/lib/systemd/timers/stamp-unbound-anchor.timer is touched every 24 hours.

Steps to Reproduce:
1. yum install unbound unbound-libs
2. systemctl start unbound.service
3. notice that /var/lib/systemd/timers/stamp-unbound-anchor.timer is touched every 24 hours

Actual results:
Not in /etc/rwtab.d/unbound

Expected results:
File should be in /etc/rwtab.d/unbound

Additional info:

Hello.

As far as I can tell, the file must be created by systemd as a side effect of running timer units. I noticed, that the /var/lib/systemd/timers/ directory contains also files for other timer units. I think the directory itself should be in rwtab and the configuration should be rather shipped by systemd.

Note that the file is not created by Unbound directly.

Agreed. Thanks for fixing the component.

After consulting this with lnykryn, we decided it would be best addressed in initscripts: https://github.com/fedora-sysv/initscripts/pull/65

We just need to backport: https://github.com/fedora-sysv/initscripts/commit/73f52775e7c92c7428759d6d41b2d39bcce541ab

Pull-request submitted:
https://github.com/fedora-sysv/initscripts/pull/84

initscripts-9.49.39-1.el7:
# grep /var/lib/systemd/timers /etc/rwtab
empty	/var/lib/systemd/timers

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, 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-2017:2286