Steps to reproduce: 1. Have Fedora 30 2. Have mdmonitor.service enabled 3. Boot Fedora 30 4. Watch syslog what happens: You'll see this warning by systemd somewhere in the syslog: > /usr/lib/systemd/system/mdmonitor.service:6: PIDFile= references path below legacy directory /var/run/, updating /var/run/mdadm/mdadm.pid → /run/mdadm/mdadm.pid; please update the unit file accordingly. What should happen: No warning Additional information: I have created a fix: https://src.fedoraproject.org/rpms/mdadm/pull-request/4 See this similar bug: https://bugzilla.redhat.com/show_bug.cgi?id=1691905
Hi Christian Could you have a try with this koji.fedoraproject.org/koji/taskinfo?taskID=34539586 This version has your patch. Thanks Xiao
I don't see the warning any more.
*** Bug 1704517 has been marked as a duplicate of this bug. ***
This issue has *NOT* been fixed. Can you please fix this issue? There is a pull request for doing that: https://src.fedoraproject.org/rpms/mdadm/pull-request/5 Also, please note @orion's comment from that pull request. Why don't you use upstream's mdmonitor.service file?
*** Bug 1716759 has been marked as a duplicate of this bug. ***
it's amazing how many month *one line fixes* in Fedora take which would have been faced by a proper QA or maintainers which look at their logs long before pushing
mdadm-4.1-1.fc31 has been pushed to the Fedora 31 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-913d180f31
mdadm-4.1-1.fc31 has been pushed to the Fedora 31 stable repository. If problems still persist, please make note of it in this bug report.