Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
Description of problem:
In RHEL-9, mdmon@.service and mdadm-grow-continue@.service use deprecated "KillMode=none" which is unsafe.
[root@localhost ~]# systemd-analyze verify mdmon@.service
/usr/lib/systemd/system/mdmon@.service:28: Unit configured to use KillMode=none. This is unsafe, as it disables systemd's process lifecycle management for the service. Please update your service to use a safer KillMode=, such as 'mixed' or 'control-group'. Support for KillMode=none is deprecated and will eventually be removed.
[root@localhost ~]# systemd-analyze verify mdadm-grow-continue@.service
/usr/lib/systemd/system/mdadm-grow-continue@.service:17: Unit configured to use KillMode=none. This is unsafe, as it disables systemd's process lifecycle management for the service. Please update your service to use a safer KillMode=, such as 'mixed' or 'control-group'. Support for KillMode=none is deprecated and will eventually be removed.
[root@localhost ~]# rpm -qf /usr/lib/systemd/system/mdadm-grow-continue@.service
mdadm-4.1-7.el9.x86_64
Version-Release number of selected components (if applicable):
RHEL Version:
RHEL-9.0(5.13.0-0.rc4.33.el9.x86_64)
How reproducible:
100%
Steps to Reproduce:
1. start a RHEL-9 with mdadm installed
2. run 'systemd-analyze verify mdmon@.service mdadm-grow-continue@.service' after boot up
Actual results:
KillMode=none is unsafe
Expected results:
Changed it to other supported safe mode
Additional info:
N/A
Hi Frank
I searched the usage of KillMode in systemd. Now it's set none which means no process is killed. But when I run
systemctl stop mdmonitor, the monitor process exit too. So I'm confused. Could you explain about this?
Thanks
Xiao
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-2022:8338