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 587995 - Correction: Incorrect path to multipath doc files
Summary: Correction: Incorrect path to multipath doc files
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: doc-DM_Multipath
Version: 6.0
Hardware: All
OS: Linux
low
low
Target Milestone: rc
: ---
Assignee: Steven J. Levine
QA Contact: ecs-bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-05-02 02:31 UTC by Justin Clift
Modified: 2010-11-11 15:27 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-11-11 15:27:40 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Justin Clift 2010-05-02 02:31:27 UTC
Description of problem:

In "Chapter 4. The DM-Multipath Configuration File", it gives explicit paths to the example multipath files installed on RHEL x.

However, in the RHEL 6 version of the guide, this is wrong.

Explicit paths mentioned:

  /usr/share/doc/device-mapper-multipath-0.4.7/multipath.conf.defaults
  /usr/share/doc/device-mapper-multipathd-0.4.7/multipath.conf.annotated

The actual paths in the present RHEL 6 beta are:

  /usr/share/doc/device-mapper-multipath-0.4.9/multipath.conf.defaults
  /usr/share/doc/device-mapper-multipath-0.4.9/multipath.conf.annotated

(It's not just the version number, there's an extra "d" in the path too)

Comment 2 RHEL Program Management 2010-05-02 03:22:28 UTC
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux major release.  Product Management has requested further
review of this request by Red Hat Engineering, for potential inclusion in a Red
Hat Enterprise Linux Major release.  This request is not yet committed for
inclusion.

Comment 4 Steven J. Levine 2010-09-20 21:48:10 UTC
I have updated the references to these paths in the RHEL 6 working draft of the DM-Multipath document. Thanks for catching this.

Comment 5 Steven J. Levine 2010-10-12 20:34:39 UTC
I am marking this bug as MODIFIED since the changes have been checked in to the SVN repository and posted on the review server.

Comment 7 Michael Doyle 2010-10-15 03:25:30 UTC
Verified in Red_Hat_Enterprise_Linux-DM_Multipath-6-en-US-1-18.

[comment] as version number change consider using 

/usr/share/doc/device-mapper-multipath-<version>/

Comment 8 releng-rhel@redhat.com 2010-11-11 15:27:40 UTC
Red Hat Enterprise Linux 6.0 is now available and should resolve
the problem described in this bug report. This report is therefore being closed
with a resolution of CURRENTRELEASE. You may reopen this bug report if the
solution does not work for you.


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