Bug List: (33 of 94)
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.
Bug 1897474 - [ppc64le] path_grouping_policy "failover" is not working normally as expected
Summary: [ppc64le] path_grouping_policy "failover" is not working normally as expected
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: device-mapper-multipath
Version: 8.4
Hardware: ppc64le
OS: Linux
unspecified
high
Target Milestone: rc
: 8.0
Assignee: Ben Marzinski
QA Contact: Storage QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-11-13 07:08 UTC by Lin Li
Modified: 2021-09-06 15:20 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-11-13 08:19:20 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Lin Li 2020-11-13 07:08:53 UTC 
Description of problem:
[ppc64le] path_grouping_policy "failover" is not working normally as expected 

Version-Release number of selected component (if applicable):
device-mapper-multipath-0.8.4-5.el8.ppc64le

How reproducible:
always

Steps to Reproduce:
1.set path_grouping_policy "failover" on IBM ppc64le server
2.[root@ibm-p9z-20-lp13 multipath]# multipathd show config
defaults {
	verbosity 2
	polling_interval 5
	max_polling_interval 20
	reassign_maps "no"
	multipath_dir "/lib64/multipath"
	path_selector "service-time 0"
	path_grouping_policy "failover"  <----------
}

3.[root@ibm-p9z-20-lp13 multipath]# multipath -ll
mpatha (3600601605e203f00d6ed8ff61e07eb11) dm-0 DGC,VRAID
size=8.0G features='1 queue_if_no_path' hwhandler='1 alua' wp=rw
|-+- policy='service-time 0' prio=50 status=active  <---------------
| |- 2:0:1:0 sdd 8:48 active ready running
| `- 1:0:1:0 sdb 8:16 active ready running
`-+- policy='service-time 0' prio=10 status=enabled    <-----------------
  |- 1:0:0:0 sda 8:0  active ready running
  `- 2:0:0:0 sdc 8:32 active ready running

4. [root@ibm-p9z-20-lp13 multipath]# echo offline >  /sys/block/sdb/device/state
[root@ibm-p9z-20-lp13 multipath]# multipath -ll
mpatha (3600601605e203f00d6ed8ff61e07eb11) dm-0 DGC,VRAID
size=8.0G features='1 queue_if_no_path' hwhandler='1 alua' wp=rw
|-+- policy='service-time 0' prio=50 status=active
| |- 2:0:1:0 sdd 8:48 active ready running
| `- 1:0:1:0 sdb 8:16 active faulty offline
`-+- policy='service-time 0' prio=10 status=enabled
  |- 1:0:0:0 sda 8:0  active ready running
  `- 2:0:0:0 sdc 8:32 active ready running

5.[root@ibm-p9z-20-lp13 multipath]# echo offline >  /sys/block/sdd/device/state
[root@ibm-p9z-20-lp13 multipath]# multipath -ll
mpatha (3600601605e203f00d6ed8ff61e07eb11) dm-0 DGC,VRAID
size=8.0G features='1 queue_if_no_path' hwhandler='1 alua' wp=rw
|-+- policy='service-time 0' prio=0 status=active
| |- 2:0:1:0 sdd 8:48 active faulty offline
| `- 1:0:1:0 sdb 8:16 failed faulty offline
`-+- policy='service-time 0' prio=10 status=enabled
  |- 1:0:0:0 sda 8:0  active ready running
  `- 2:0:0:0 sdc 8:32 active ready running

6.[root@ibm-p9z-20-lp13 multipath]# multipath -ll
mpatha (3600601605e203f00d6ed8ff61e07eb11) dm-0 DGC,VRAID
size=8.0G features='1 queue_if_no_path' hwhandler='1 alua' wp=rw
|-+- policy='service-time 0' prio=0 status=enabled
| |- 2:0:1:0 sdd 8:48 failed faulty offline
| `- 1:0:1:0 sdb 8:16 failed faulty offline
`-+- policy='service-time 0' prio=10 status=enabled
  |- 1:0:0:0 sda 8:0  active ready running
  `- 2:0:0:0 sdc 8:32 active ready running

7.[root@ibm-p9z-20-lp13 multipath]# dd if=/dev/zero of=/dev/mapper/mpatha
dd: writing to '/dev/mapper/mpatha': No space left on device
16777217+0 records in
16777216+0 records out
8589934592 bytes (8.6 GB, 8.0 GiB) copied, 74.9968 s, 115 MB/s

8.[root@ibm-p9z-20-lp13 multipath]# multipath -ll
mpatha (3600601605e203f00d6ed8ff61e07eb11) dm-0 DGC,VRAID
size=8.0G features='1 queue_if_no_path' hwhandler='1 alua' wp=rw
`-+- policy='service-time 0' prio=50 status=active
  |- 2:0:1:0 sdd 8:48 failed faulty offline
  |- 1:0:1:0 sdb 8:16 failed faulty offline
  |- 1:0:0:0 sda 8:0  active ready running
  `- 2:0:0:0 sdc 8:32 active ready running

Actual results:
 path_grouping_policy become "multibus"

Expected results:
path_grouping_policy should be "failover", The second path group should become active instead of 4 paths in the same path group.
like:
[root@ibm-p9z-20-lp13 multipath]# multipath -ll
mpatha (3600601605e203f00d6ed8ff61e07eb11) dm-0 DGC,VRAID
size=8.0G features='1 queue_if_no_path' hwhandler='1 alua' wp=rw
|-+- policy='service-time 0' prio=0 status=enabled  <---------------
| |- 2:0:1:0 sdd 8:48 failed faulty offline
| `- 1:0:1:0 sdb 8:16 failed faulty offline
`-+- policy='service-time 0' prio=10 status=active    <-----------------
  |- 1:0:0:0 sda 8:0  active ready running
  `- 2:0:0:0 sdc 8:32 active ready running


Additional info:
Note You need to log in before you can comment on or make changes to this bug.
Bug List: (33 of 94)