Bug 249088
| Summary: | device-mapper-multipath has wrong path for mpath_prio_hds_modular | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 5 | Reporter: | Bryn M. Reeves <bmr> | ||||
| Component: | device-mapper-multipath | Assignee: | Ben Marzinski <bmarzins> | ||||
| Status: | CLOSED ERRATA | QA Contact: | Corey Marthaler <cmarthal> | ||||
| Severity: | medium | Docs Contact: | |||||
| Priority: | medium | ||||||
| Version: | 5.0 | CC: | agk, bmarzins, christophe.varoqui, djuran, dwysocha, egoggin, junichi.nomura, kueda, lmb, mbroz, poelstra, prockai, tranlan | ||||
| Target Milestone: | --- | Keywords: | OtherQA | ||||
| Target Release: | --- | ||||||
| Hardware: | All | ||||||
| OS: | Linux | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | RHBA-2008-0337 | Doc Type: | Bug Fix | ||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2008-05-21 15:35:20 UTC | Type: | --- | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Attachments: |
|
||||||
Created attachment 159687 [details]
fix mpath_prio_hds_modular path
I have this patch running on 100s of machines here at Hitachi and in the field. It is good. ccb This request was evaluated by Red Hat Product Management for inclusion in a Red Hat Enterprise Linux maintenance release. Product Management has requested further review of this request by Red Hat Engineering, for potential inclusion in a Red Hat Enterprise Linux Update release for currently deployed products. This request is not yet committed for inclusion in an Update release. Patch applied. Thanks. QE ack for RHEL5.2. Will lean on partners for validation. Greetings Red Hat Partner, A fix for this issue should be included in the latest packages contained in RHEL5.2-Snapshot1--available now on partners.redhat.com. Please test and confirm that your issue is fixed. After you (Red Hat Partner) have verified that this issue has been addressed, please perform the following: 1) Change the *status* of this bug to VERIFIED. 2) Add *keyword* of PartnerVerified (leaving the existing keywords unmodified) If this issue is not fixed, please add a comment describing the most recent symptoms of the problem you are having and change the status of the bug to ASSIGNED. If you are receiving this message in Issue Tracker, please reply with a message to Issue Tracker about your results and I will update bugzilla for you. If you need assistance accessing ftp://partners.redhat.com, please contact your Partner Manager. Thank you An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on the solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHBA-2008-0337.html |
Description of problem: The compiled in default priority callout for the Hitachi HDS SANs is incorrectly specified without the full path in libmultipath/hwtable.c: { .vendor = "HITACHI", .product = "DF.*", .getuid = DEFAULT_GETUID, .getprio = "mpath_prio_hds_modular %d", .features = DEFAULT_FEATURES, .hwhandler = DEFAULT_HWHANDLER, .selector = DEFAULT_SELECTOR, .pgpolicy = GROUP_BY_PRIO, .pgfailback = -FAILBACK_IMMEDIATE, .rr_weight = RR_WEIGHT_NONE, .no_path_retry = NO_PATH_RETRY_UNDEF, .minio = DEFAULT_MINIO, .checker_name = READSECTOR0, }, This leads to errors like: error calling out mpath_prio_hds_modular 65:32 error calling out mpath_prio_hds_modular 66:80 error calling out mpath_prio_hds_modular 65:32 Version-Release number of selected component (if applicable): multipath-tools-0.4.7.rhel5.5 How reproducible: 100% Steps to Reproduce: 1. Enable multipath on a system attached to a Hitachi HDS SAN by commenting out the blacklist {...} block in multipath.conf 2. Run multipath Actual results: Above errors Expected results: No errors, correctly determines path prio grouping & creates multipath maps Additional info: Easily worked around via multipath.conf device {...} blocks.