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 1464633 - Device-mapper-multipath configuration of Huawei Storage need to be upgraded
Summary: Device-mapper-multipath configuration of Huawei Storage need to be upgraded
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: device-mapper-multipath
Version: 6.10
Hardware: x86_64
OS: Linux
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Ben Marzinski
QA Contact: Lin Li
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-06-24 01:55 UTC by zhouweigang09
Modified: 2017-12-06 10:21 UTC (History)
10 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-12-06 10:21:21 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description zhouweigang09 2017-06-24 01:55:46 UTC
Hi,
  We submitted a bug to integrate Huawei storage's multipath configuration in RHEL system by default with bug 1333334,and we found it works well with RHEL 6.9.
  Now we want to upgrade the configuration from later RHEL v6 versions as follows:
  device {
      vendor                      "HUAWEI"
      product                     "XSG1"
      path_grouping_policy        group_by_prio
      getuid_callout              "/lib/udev/scsi_id --whitelisted --device=/dev/%n"
      prio                        alua
      path_checker                tur
      path_selector              “round-robin 0“     
      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-11-02 03:37:09 UTC
Hello zhouweigang,
Could you provide test result once the fixed version is available?
Thanks in advance.

Comment 3 zhouweigang09 2017-11-02 03:45:59 UTC
Hello Lin li,

Sure,we will tell you the result as soon as we finish the test.

Comment 4 Jan Kurik 2017-12-06 10:21:21 UTC
Red Hat Enterprise Linux 6 is in the Production 3 Phase. During the Production 3 Phase, Critical impact Security Advisories (RHSAs) and selected Urgent Priority Bug Fix Advisories (RHBAs) may be released as they become available.

The official life cycle policy can be reviewed here:

http://redhat.com/rhel/lifecycle

This issue does not meet the inclusion criteria for the Production 3 Phase and will be marked as CLOSED/WONTFIX. If this remains a critical requirement, please contact Red Hat Customer Support to request a re-evaluation of the issue, citing a clear business justification. Note that a strong business justification will be required for re-evaluation. Red Hat Customer Support can be contacted via the Red Hat Customer Portal at the following URL:

https://access.redhat.com/


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