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 1830736 - mdcheck_start.timer Failed to parse calendar specification
Summary: mdcheck_start.timer Failed to parse calendar specification
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: mdadm
Version: 7.8
Hardware: Unspecified
OS: Unspecified
urgent
unspecified
Target Milestone: rc
: ---
Assignee: XiaoNi
QA Contact: Fine Fan
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-05-03 14:59 UTC by Andrew Bauer
Modified: 2024-12-20 19:04 UTC (History)
12 users (show)

Fixed In Version: mdadm-4.1-8.el7_9
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-11-23 17:12:55 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Knowledge Base (Solution) 5753411 0 None None None 2021-11-24 14:54:06 UTC
Red Hat Product Errata RHBA-2021:4775 0 None None None 2021-11-23 17:12:56 UTC

Description Andrew Bauer 2020-05-03 14:59:16 UTC 
Description of problem
----------------------
Systemd version 219 on CentOS 7 does not recognize the ".." range parameter, which causes the mdcheck_start.timer to fail.

Version-Release number of selected component (if applicable):
mdadm-4.1-4.el7.x86_64


Steps to Reproduce
------------------
1. yum install mdadm
2. systemctl status -l mdcheck_start.timer


Actual results
--------------
● mdcheck_start.timer - MD array scrubbing
   Loaded: error (Reason: Invalid argument)
   Active: inactive (dead)

May 03 09:29:22 localhost systemd[1]: [/usr/lib/systemd/system/mdcheck_start.timer:12] Failed to parse calendar specification, ignoring: Sun *-*-1..7 1:00:00
May 03 09:29:22 localhost systemd[1]: mdcheck_start.timer lacks value setting. Refusing.
May 03 09:32:09 localhost systemd[1]: [/usr/lib/systemd/system/mdcheck_start.timer:12] Failed to parse calendar specification, ignoring: Sun *-*-1..7 1:00:00
May 03 09:32:09 localhost systemd[1]: mdcheck_start.timer lacks value setting. Refusing.


Expected results
-----------------
timer runs successfully


Additional info
----------------
Changing the OnCalendar line in mdcheck_start.timer to the following allows the timer to run successfully:
>OnCalendar=Sun *-*-01,02,03,04,05,06,07 01:00:00


Once this is resolved in the package, please evaluate whether the legacy cron file is still needed:
>$ rpm -ql mdadm |grep cron
>/etc/cron.d/raid-check
Comment 17 errata-xmlrpc 2021-11-23 17:12:55 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (mdadm bug fix and enhancement update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2021:4775
Note You need to log in before you can comment on or make changes to this bug.