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.

For RHEL 6.3, support for some configuration file parameters was added to the devices section of the multipath.conf file. Check against this info to be sure we have it all correct in the latest document (info received from Ben Marzinski):

> user_friendly_names:
> configurable in multipaths section for 6.3?
yes
> configurable in devices section for 6.3?
yes

> flush_on_last_del
> configurable in multipaths section for 6.3?
yes
> configurable in devices section for 6.3?
yes

> max_fds
> configurable in multipaths section for 6.3?
no
> configurable in devices section for 6.3?
no

> queue_without_daemon
> configurable in multipaths section for 6.3?
no
> configurable in devices section for 6.3?
no

All of these defaults are documented in the appropriate tables, so there are not fixes here. Closing this bug.

Changing status to closed current release -- it was a bug, but it's already in the published document, so that seems a better fit.