Bug 1464634 – Device-mapper-multipath configuration of Huawei Storage need to be upgraded

Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.

Bug 1464634 - Device-mapper-multipath configuration of Huawei Storage need to be upgraded [NEEDINFO]

Summary:	Device-mapper-multipath configuration of Huawei Storage need to be upgraded

Status:	CLOSED ERRATA

Aliases:	None

Product:	Red Hat Enterprise Linux 7
Classification:	Red Hat
Component:	device-mapper-multipath (Show other bugs)
Sub Component:
Version:	7.4
Hardware:	x86_64 Linux

Priority	unspecified Severity unspecified
Target Milestone:	rc
Target Release:	---
Assigned To:	Ben Marzinski
QA Contact:	Lin Li
Docs Contact:

URL:
Whiteboard:
Keywords:	OtherQA

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2017-06-23 22:02 EDT by zhouweigang09
Modified:	2018-04-10 12:10 EDT (History)
CC List:	9 users (show)

See Also:
Fixed In Version:	device-mapper-multipath-0.4.9-114.el7
Doc Type:	No Doc Update
Doc Text:	undefined
Story Points:	---
Clone Of:
Environment:
Last Closed:	2018-04-10 12:10:28 EDT
Type:	Bug
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Flags:	lilin: needinfo? (zhouweigang09)

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

External Trackers
Tracker	ID	Priority	Status	Summary	Last Updated
Red Hat Product Errata	RHEA-2018:0884	normal	SHIPPED_LIVE	device-mapper-multipath bug fix and enhancement update	2018-04-10 09:47:14 EDT

Groups: None (edit)

Description zhouweigang09 2017-06-23 22:02:44 EDT

Hi,
  We submitted a bug to integrate Huawei storage's multipath configuration in RHEL system by default with bug 1333331,and we found it works well with RHEL 7.3.
  Now we want to upgrade the configuration from later RHEL v7 versions as follows:
  device {
      vendor                      "HUAWEI"
      product                     "XSG1"
      path_grouping_policy        group_by_prio
      prio                        alua
      path_checker                tur     
      failback                    immediate
      fast_io_fail_tmo            5 
      dev_loss_tmo                30
      detect_prio                 no
      retain_attached_hw_handler “no”
      hardware_handler            0
}
   This configuration will enable the ALUA feature by default ,could you please help us to achieve that.

Thanks

Comment 2 Lin Li 2017-07-12 21:35:47 EDT

Hello huawei，
Could you provide test result once the package is available?
Thanks.

Comment 3 zhouweigang09 2017-07-24 07:44:53 EDT

sure, I'll give the test result this week.
Thanks.

Comment 4 zhouweigang09 2017-07-24 07:52:16 EDT

sorry, my mistake.
we'll test it when the package is available.

Comment 5 Ben Marzinski 2017-10-04 19:31:02 EDT

Updated the built in configuration.

Comment 9 Lin Li 2018-01-03 02:49:44 EST

Hello weigang,
Because we don't have Huawei storage, we can only check default configuration.
Could you help check if it works normally for you?
Thanks in advance.

Comment 10 Lin Li 2018-01-27 11:44:08 EST

(In reply to Lin Li from comment #9)
> Hello weigang,
> Because we don't have Huawei storage, we can only check default
> configuration.
> Could you help check if it works normally for you?
> Thanks in advance.

Any update?

Comment 11 Lin Li 2018-02-05 02:03:34 EST

Hello weigang,
Because we don't have Huawei storage, we can only check default configuration.
Could you help check if it works normally for you?
Thanks in advance.

Comment 13 Lin Li 2018-02-19 03:49:38 EST

move to verified+sanityonly because the deadline is coming.

Comment 16 errata-xmlrpc 2018-04-10 12:10:28 EDT

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, 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/RHEA-2018:0884

Note You need to log in before you can comment on or make changes to this bug.