Description of problem: Hi all In 4.1-3, mdadm added raid-check.timer. It needs to enable raid-check.timer by default Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
*** Bug 1817492 has been marked as a duplicate of this bug. ***
Please answer the following questions: * Does the service require post-rpm-installation configuration in order to be useful (for example, does it need manual edits to a configuration file)? * Does the service listen on a network socket for connections originating on a separate physical or virtual machine? * Is the service non-persistent (i.e. run once at startup and exit)? * What is the exact name (or names) of the systemd unit files to be enabled? * Is this request for all Fedora deliverables or only for some Editions (list them)?
(In reply to Zbigniew Jędrzejewski-Szmek from comment #2) > Please answer the following questions: > > * Does the service require post-rpm-installation configuration in order to > be useful (for example, does it need manual edits to a configuration file)? Hi Does it mean it needs this line in spec file? %systemd_post mdmonitor.service raid-check.{service,timer} It doesn't need to edit raid-check.service and raid-check.timer manually. > > * Does the service listen on a network socket for connections originating on > a separate physical or virtual machine? No > > * Is the service non-persistent (i.e. run once at startup and exit)? It's raid-check.timer [Unit] Description=Weekly RAID setup health check [Timer] OnCalendar=Sun *-*-* 01:00:00 Persistent=true AccuracySec=24h [Install] WantedBy=timers.target So it's persistent, right? > > * What is the exact name (or names) of the systemd unit files to be enabled? /usr/lib/systemd/system/raid-check.timer > > * Is this request for all Fedora deliverables or only for some Editions > (list them)? f31/f32/rawhide
Hi all Any update on this one?
Hi all Any update on this one? Now it affects mdadm systemd raid-check service.
Submitted for inclusion to fedora-release: https://src.fedoraproject.org/rpms/fedora-release/pull-request/131
Hi Stephen This bug is not fixed. The steps should be wrong. It needs to run fedpkg update. Maybe it's the reason? https://bugzilla.redhat.com/show_bug.cgi?id=1801010#c37 Thanks Xiao
Hi Stephen Do I need to file a new bug for f32/f31?
No, I can use this one to add it to F32. There's no point in submitting it for F31 now; it goes EOL in 11 days (and would likely take at least seven to get to the stable repo).
FEDORA-2020-202ff77470 has been submitted as an update to Fedora 32. https://bodhi.fedoraproject.org/updates/FEDORA-2020-202ff77470
FEDORA-2020-202ff77470 has been pushed to the Fedora 32 stable repository. If problem still persists, please make note of it in this bug report.