Bug 456457 - multipath does not read a section in multipath.conf unless it has a space before the open bracket.
multipath does not read a section in multipath.conf unless it has a space bef...
Status: CLOSED ERRATA
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: device-mapper-multipath (Show other bugs)
4.6
All Linux
low Severity low
: rc
: ---
Assigned To: Ben Marzinski
Corey Marthaler
:
Depends On:
Blocks: 456458
  Show dependency treegraph
 
Reported: 2008-07-23 16:16 EDT by Ben Marzinski
Modified: 2010-01-11 21:32 EST (History)
14 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
* multipath could not parse entries in the multipath.conf files if there was no space between the section name and the open bracket that followed it (for example, "blacklist{" instead of "blacklist {") and would simply ignore such entries. Multipath now recognizes and parses entries without spaces.
Story Points: ---
Clone Of:
Environment:
Last Closed: 2009-05-18 16:32:05 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Ben Marzinski 2008-07-23 16:16:53 EDT
Description of problem:

In a multipath.conf file.  If a section doesn't have a space between the section
name and the open bracket, that section isn't read in.  For instance

blacklist {
        devnode "*"
}

correctly blacklists all devices, but

blacklist{
        devnode "*"
}

does nothing.
Comment 1 Ben Marzinski 2009-01-19 17:56:31 EST
This was an error in the parser function.  It wasn't recognizing the bracket as separate from the section name.  Fixed.
Comment 3 Ruediger Landmann 2009-02-02 00:53:38 EST
Release note added. If any revisions are required, please set the 
"requires_release_notes" flag to "?" and edit the "Release Notes" field accordingly.
All revisions will be proofread by the Engineering Content Services team.

New Contents:
* multipath could not parse entries in the multipath.conf files if there was no space between the section name and the open bracket that followed it (for example, "blacklist{" instead of "blacklist {") and would simply ignore such entries. Multipath now recognizes and parses entries without spaces.
Comment 5 errata-xmlrpc 2009-05-18 16:32:05 EDT
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 therefore 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-2009-1011.html

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