Description of problem: Each time dhcpd.service is (re)started, dhcpd.leases is recreated with root.root ownership instead of dhcpd.dhcpd. The incorrect ownership persists until dhcpd writes the leases again (hours later). This doesn't seem to hurt the operation of dhcpd, but it does cause "rpm -V dhcp" to report a UG (user+group) discrepancy on the leases file. Version-Release number of selected component (if applicable): dhcp-4.2.3-8.P2.fc16 How reproducible: Always Steps to Reproduce: 1. servicectl restart dhcpd.service 2. Check ownership of dhcpd.leases Actual results: root.root Expected results: dhcpd.dhcpd
Yes, I know about it and I already tried to change this but with no luck, see bug #765967, comment #1. This is the least painful solution and I'm afraid we need to live with it. Thanks for the report anyway.
Could you please add "owner" and "group" to the list of %verify exclusions on the leases files, then? i.e. %verify(not size md5 mtime owner group) If the ownership changes are considered normal -- just as size/md5/mtime changes are -- then it seems appropriate for "rpm -V" to not report them. The reason I care: I have a cron job that runs "rpm -Va" periodically and alerts me if any new discrepancies are found. The ownership flip-flop here keeps triggering unwanted alerts whenever I reboot or otherwise restart dhcpd.
Jordan, please test https://koji.fedoraproject.org/koji/buildinfo?buildID=329625
dhcp-4.2.4-6.fc17 has been submitted as an update for Fedora 17. https://admin.fedoraproject.org/updates/dhcp-4.2.4-6.fc17
dhcp-4.2.3-9.P2.fc16 has been submitted as an update for Fedora 16. https://admin.fedoraproject.org/updates/dhcp-4.2.3-9.P2.fc16
Package dhcp-4.2.3-9.P2.fc16: * should fix your issue, * was pushed to the Fedora 16 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing dhcp-4.2.3-9.P2.fc16' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2012-11018/dhcp-4.2.3-9.P2.fc16 then log in and leave karma (feedback).
dhcp-4.2.4-7.P1.fc17 has been submitted as an update for Fedora 17. https://admin.fedoraproject.org/updates/dhcp-4.2.4-7.P1.fc17
dhcp-4.2.3-10.P2.fc16 has been submitted as an update for Fedora 16. https://admin.fedoraproject.org/updates/dhcp-4.2.3-10.P2.fc16
/var/lib/dhcpd.leases is still given root:root ownership if dhcpd.service is restarted. If ownership is changed to dhcpd:dhcpd then it is changed back to root:root when dhcpd is restarted.
The rpm -V dhcp does not report any discrepancy on the leases file but the file ownership remains incorrect. It is not clear if the "fix" was merely to stop the discrepancy report or actually fix the ownership problem?
As I stated in comment #1 I have no idea how to properly fix this ownership problem so this updates only brings what you suggested in comment #2, i.e. it makes 'rpm -V' stop complaining about owner/group of dhcpd.leases file.
No problem - I gave it positive karma anyway in bodhi - hopefully the new version will go through soon - it works fine for me.
dhcp-4.2.4-9.P1.fc17 has been pushed to the Fedora 17 stable repository. If problems still persist, please make note of it in this bug report.
dhcp-4.2.3-11.P2.fc16 has been pushed to the Fedora 16 stable repository. If problems still persist, please make note of it in this bug report.