Bug 1774354 - mdcheck_continue.service cannot be started due to Invalid environment assignment, ignoring: MDADM_CHECK_DURATION='"6 hours"' [NEEDINFO]
Summary: mdcheck_continue.service cannot be started due to Invalid environment assignm...
Keywords:
Status: ASSIGNED
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: mdadm
Version: 7.7
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: XiaoNi
QA Contact: Storage QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-11-20 05:43 UTC by mezhang
Modified: 2019-12-06 17:31 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Target Upstream Version:
mezhang: needinfo? (ncroxon)


Attachments (Terms of Use)

Description mezhang 2019-11-20 05:43:43 UTC
Description of problem:
mdcheck_continue.service cannot be started due to Invalid environment assignment, ignoring: MDADM_CHECK_DURATION='"6 hours"' in rhel7.7

Version-Release number of selected component (if applicable):
kernel-3.10.0-1062.el7.x86_64
mdadm-4.1-1.el7.x86_64

How reproducible:

new OS. 
install mdadm package and reboot OS. you will get this error in /var/log/messages.

~~~
Nov 20 00:19:30 rhel7u7 systemd[1]: [/usr/lib/systemd/system/mdcheck_continue.service:14] Invalid environment assignment, ignoring: MDADM_CHECK_DURATION='"6 hours"'
Nov 20 00:19:42 rhel7u7 systemd[1]: [/usr/lib/systemd/system/mdcheck_continue.service:14] Invalid environment assignment, ignoring: MDADM_CHECK_DURATION='"6 hours"'

~~~

Actual results:

# systemctl status mdcheck_continue.service  -l
● mdcheck_continue.service - MD array scrubbing - continuation
   Loaded: loaded (/usr/lib/systemd/system/mdcheck_continue.service; static; vendor preset: disabled)
   Active: inactive (dead)

Nov 19 22:34:48 rhel7u7 systemd[1]: [/usr/lib/systemd/system/mdcheck_continue.service:14] Invalid environment assignment, ignoring: MDADM_CHECK_DURATION='"6 hours"'
Nov 20 00:19:21 rhel7u7 systemd[1]: [/usr/lib/systemd/system/mdcheck_continue.service:14] Invalid environment assignment, ignoring: MDADM_CHECK_DURATION='"6 hours"'
Nov 20 00:19:30 rhel7u7 systemd[1]: [/usr/lib/systemd/system/mdcheck_continue.service:14] Invalid environment assignment, ignoring: MDADM_CHECK_DURATION='"6 hours"'
Nov 20 00:19:42 rhel7u7 systemd[1]: [/usr/lib/systemd/system/mdcheck_continue.service:14] Invalid environment assignment, ignoring: MDADM_CHECK_DURATION='"6 hours"'


Expected results:
 mdcheck_continue.service will be started normally.

Comment 2 Nigel Croxon 2019-11-21 17:09:34 UTC
The OS comes with userspace tool mdadm installed by default.

What optional packages did you check off during installation?

Comment 3 mezhang 2019-11-22 03:34:04 UTC
>What optional packages did you check off during installation?

I didn't install additional optional packages during installation.

Besides, my test environment is a vm.

Mengyi

Comment 4 mezhang 2019-11-22 03:52:55 UTC
Hi 

Addition error log is outputted. The detail is as below:

~~~
/usr/lib/systemd/system/mdcheck_start.timer:12] Failed to parse calendar specification, ignoring: Sun *-*-1..7 1:00:00
~~~

# cat /usr/lib/systemd/system/mdcheck_start.timer
#  This file is part of mdadm.
#
#  mdadm is free software; you can redistribute it and/or modify it
#  under the terms of the GNU General Public License as published by
#  the Free Software Foundation; either version 2 of the License, or
#  (at your option) any later version.

[Unit]
Description=MD array scrubbing

[Timer]
OnCalendar=Sun *-*-1..7 1:00:00   <--- 

[Install]
WantedBy= mdmonitor.service

Thank you.

Comment 5 MatthewH 2019-12-04 08:35:58 UTC
I’m getting the same issue downstream on CentOS 7.7 (see their issue https://bugs.centos.org/view.php?id=16665 )

As far as I can tell the problem is the systemd components included in the latest mdadm package are incompatible with the version of systemd included with RHEL/CentOS 7.

In my case I don’t just see these errors, but also can no longer automount my RAID array due to systemd ordering cycle problems.

Thanks


Note You need to log in before you can comment on or make changes to this bug.