Description of problem: SSIA Version-Release number of selected component (if applicable): mdadm-4.1-4.fc31.x86_64 How reproducible: N/A Steps to Reproduce: edit /etc/sysconfig/raid-check Check the file: # Configuration file for /etc/cron.weekly/raid-check Actual results: /etc/cron.weekly/raid-check does not exist. Expected results: # Configuration file for /lib/systemd/system/raid-check.timer Additional info: This breaking change in the middle of a Fedora stable release trashes all the releng alpha/beta and go/no-go efforts.
Also I think at least raid-check.timer should be marked as %config but packaging guidelines say either nothing or probably the opposite: https://fedoraproject.org/wiki/Packaging:Systemd#.25files_section
> Also I think at least raid-check.timer should be marked as %config but Not in /usr/lib/systemd/system/ it shouldn't, you should copy it to /etc/systemd/system/ if you want to edit it with a custom time, anything in /usr shouldn't be edited and hence config
This message is a reminder that Fedora 31 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 31 on 2020-11-24. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '31'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 31 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
The reference to the cron file is still there. Please continue to use cron files! Nobody is expecting some obscure systemd stuff there, and systemd is way too cryptic without trying to ursurp the function of crond. This is going too far. Change it back to using a cron file!
PS: "Still there" refers to Fedora 33. How can I verify that an email is being sent to me in case a disk failure is being detected?
Still valid: mdadm-4.1-6.fc33.x86_64
This message is a reminder that Fedora 33 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 33 on 2021-11-30. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '33'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 33 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 33 changed to end-of-life (EOL) status on 2021-11-30. Fedora 33 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.