Bug 2130226

Summary: multipathd sometimes shows "marginal_paths fpin", sometimes shows "marginal_paths off"
Product: Red Hat Enterprise Linux 9 Reporter: Lin Li <lilin>
Component: device-mapper-multipathAssignee: Ben Marzinski <bmarzins>
Status: CLOSED MIGRATED QA Contact: Lin Li <lilin>
Severity: high Docs Contact:
Priority: high    
Version: 9.1CC: agk, bmarzins, heinzm, jbrassow, msnitzer, nyewale, prajnoha, zkabelac
Target Milestone: rcKeywords: MigratedToJIRA, Triaged
Target Release: ---Flags: pm-rhel: mirror+
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-09-23 18:35:35 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Lin Li 2022-09-27 14:52:30 UTC
Description of problem:
multipathd sometimes shows "marginal_paths fpin", sometimes shows  "marginal_paths off"

Version-Release number of selected component (if applicable):
device-mapper-multipath-0.8.7-12.el9.x86_64

How reproducible:
sometimes

Steps to Reproduce:
1.yum -y install device-mapper-multipath
2.rpm -qa | grep multipath
3./sbin/mpathconf --enable
4.service multipathd restart
5.edit /etc/multipath.conf
defaults {
        marginal_pathgroups off 
	user_friendly_names yes
	find_multipaths yes
}
6.service multipathd reload
7.multipathd show config 2>&1 | grep -E marginal_pathgroups

8.repeat step 5-7
#multipathd show config | grep marginal_pathgroups
	sometimes shows marginal_pathgroups "fpin"
        sometimes shows marginal_pathgroups "off"


Actual results:


Expected results:
#multipathd show config | grep marginal_pathgroups
	always shows marginal_pathgroups "fpin"

Additional info:

Comment 2 Ben Marzinski 2022-11-23 21:22:16 UTC
I was never able to get marginal_pathgroups to switch values on a multipathd reload. That should be the case, because you are not allowed to switch the marginal_pathgroups setting either to or from "fpin" on a reconfigure.  It needs to be there from when multipathd starts up to work correctly. If you look in the log messages you posted, you can see lines like:

Sep 26 07:22:43 storageqe-05 multipathd[32057]: reconfigure (operator)
Sep 26 07:22:43 storageqe-05 multipathd[33045]: ok
Sep 26 07:22:43 storageqe-05 multipathd[32057]: multipathd must be restarted to turn off fpin marginal paths

The same thing happens if you start with marginal_pathgroups set to something other than fpin, and try to change it to fpin on a reload. You say that it did change sometimes, but is it possible that occasionally you ran

# service multipathd restart

instead of

# service mulitpathd reload

In this case it would be able to change. If you can still reproduce this, sending me a script to do it would be helpful, since I couldn't make it switch randomly when I tried.

Comment 3 RHEL Program Management 2023-09-23 18:22:30 UTC
Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug.

Comment 4 RHEL Program Management 2023-09-23 18:35:35 UTC
This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.