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:


Version-Release number of selected component (if applicable):
device-mapper-multipath-0.4.9-51.el7.x86_64


How reproducible:
100%

Steps to Reproduce:

# multipathd forcequeueing daemon
ok
# multipathd show config > /opt/1
# multipath -t > /opt/2
# diff /opt/1 /opt/2
17c17
< 	queue_without_daemon "forced"
---
> 	queue_without_daemon "no"

Actual results:
multipath -t report the previous queue_without_daemon value

Expected results:


Additional info:

Since you're manually setting the state of the daemon, it's going to be different than the configuration file.  There is no way for the multipath command to know that you did this.   Also, there is no reason for it to really care.  queue_without_daemon "no" simply turns queuing off when the multipathd daemon exist.  The multipath command never checks the queue_without_daemon value except to print it with -t. Thus, it's perfectly safe for it to not know that you manually overrode the configuration on the daemon.