This bug has been migrated to another issue tracking site. It has been closed here and may no longer be being monitored.

If you would like to get updates for this issue, or to participate in it, you may do so at Red Hat Issue Tracker .
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.
Bug 2232836 - No software RAID scrub/check scheduled by default
Summary: No software RAID scrub/check scheduled by default
Keywords:
Status: CLOSED MIGRATED
Alias: None
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: mdadm
Version: 9.2
Hardware: x86_64
OS: Linux
unspecified
low
Target Milestone: rc
: ---
Assignee: XiaoNi
QA Contact: Storage QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-08-19 10:17 UTC by g.danti
Modified: 2023-09-23 19:23 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-09-23 19:23:34 UTC
Type: Bug
Target Upstream Version:
Embargoed:
pm-rhel: mirror+

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker   RHEL-8374 0 None Migrated None 2023-09-23 19:23:35 UTC
Red Hat Issue Tracker RHELPLAN-166038 0 None None None 2023-08-19 10:21:06 UTC

Description g.danti 2023-08-19 10:17:22 UTC 
Description of problem:
In previous RHEL version, a cron entry existed for automatic scrub of software RAID arrays. In current RHEL 9.x two services called mdcheck_start.service and mdcheck_continue.service are provided, and they can be triggered by the respective systemd timers. However they call a non-existing script at path /usr/share/mdadm/mdcheck. The mdcheck script really lives at /usr/share/doc/mdadm/mdcheck. 

Indeed, checking which packages provides the mdcheck script shows:

# yum whatprovides */mdcheck
Last metadata expiration check: 2:21:21 ago on Sat 19 Aug 2023 09:40:01 AM CEST.
mdadm-4.2-8.el9.x86_64 : The mdadm program controls Linux md devices (software RAID arrays)
Repo        : @System
Matched from:
Filename    : /usr/share/doc/mdadm/mdcheck

As things stand now, one has to create a custom cron entry or softlink the /usr/share/doc/mdadm/mdcheck at the path expected by the systemd services (ie: ln -s /usr/share/doc/mdadm/mdcheck /usr/share/mdadm/mdcheck)

Version-Release number of selected component (if applicable):
mdadm-4.2-8.el9.x86_64

How reproducible:
Try starting mdcheck_start.service and see how it fails due to a non-existent ExecStart path.

Steps to Reproduce:
1. systemctl start mdcheck_start.service
2. systemctl status mdcheck_start.service
3. the service is in failed state

Actual results:
mdcheck_start.service and mdcheck_continue.service do not start, nor classical cron entry is provided for software RAID scrub/check

Expected results:
Automatic software RAID scrub/check should be provided out of the box.

Additional info:
None.
Comment 1 RHEL Program Management 2023-09-23 19:21:54 UTC 
Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug.
Comment 2 RHEL Program Management 2023-09-23 19:23:34 UTC 
This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.
Note You need to log in before you can comment on or make changes to this bug.