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.
Multipath now has improved checking of multipath.conf values. However, this error checking is still more limited than what you are testing for. For numeric values with ranges, multipath.conf will now cap the values to the range. For values with keywords, multipath will now print a message if the keyword is invalid. There are a couple of other checks. However, for values that are arbitrary strings, multipath does not do any checking, since it doesn't know which values will be accepted. This depends on things like which kernel modules exist on the system. For instance, if the service-time path selector module exists, then
path_selector "service-time 0"
is valid. If that module doesn't exist, it isn't.
This amount of error checking is what is acceptable upstream.
Verified on device-mapper-multipath-0.8.7-3.el9
[root@storageqe-25 ~]# rpm -qa | grep multipath
device-mapper-multipath-libs-0.8.7-3.el9.x86_64
device-mapper-multipath-0.8.7-3.el9.x86_64
[root@storageqe-25 ~]# man multipath.conf
defaults section
The defaults section recognizes the following keywords:
verbosity Default verbosity. Higher values increase the ver‐
bosity level. Valid levels are between 0 and 6.
The default is: 2
Edit /etc/multipath.conf
[root@storageqe-25 ~]# cat /etc/multipath.conf
defaults {
user_friendly_names yes
find_multipaths yes
verbosity 8 <--------------------------------
}
[root@storageqe-25 ~]# multipath -ll
53929.624073 | /etc/multipath.conf line 14, value for verbosity too large, capping at 4
Test result: For numeric values with ranges, multipath.conf will now cap the values to the range.
Edit /etc/multipath.conf
[root@storageqe-25 ~]# cat /etc/multipath.conf
defaults {
user_friendly_names yes
find_multipaths yes
#verbosity 8
foo 2 <-----------------------------
}
[root@storageqe-25 ~]# service multipathd reload
Redirecting to /bin/systemctl reload multipathd.service
[root@storageqe-25 ~]# multipath -ll
54170.516702 | /etc/multipath.conf line 15, invalid keyword in the defaults section: foo <-----------------------------
360a98000324669436c2b45666c567858 dm-3 NETAPP,LUN
size=2.0G features='3 queue_if_no_path pg_init_retries 50' hwhandler='1 alua' wp=rw
|-+- policy='service-time 0' prio=50 status=active
| |- 6:0:1:0 sdf 8:80 active ready running
| `- 8:0:1:0 sdn 8:208 active ready running
`-+- policy='service-time 0' prio=10 status=enabled
|- 6:0:0:0 sdb 8:16 active ready running
`- 8:0:0:0 sdj 8:144 active ready running
Test result:For values with keywords, multipath will now print a message if the keyword is invalid.
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 (new packages: device-mapper-multipath), 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:3971