multipath.conf is modified incorrectly when using MultipathdCustomConfigFile parameter

Solution Verified - Updated -

Issue

  • MultipathdCustomConfigFile is declared in a template file to deploy a specific multipath.conf file.
  • However, multipath.conf is modified wrongly after deploying overcloud.

    <Original multipath.conf>
    blacklist {
        devnode "^(ram|raw|loop|fd|md|dm-|sr|scd|st)[0-9]*"
        devnode "^hd[a-z]"
    }
    
    blacklist_exceptions {
        device {
            product "XXXX"
            vendor "XXXX"
        }
    }
    
    <Deployed multipath.conf file on overcloud Compute node>
    blacklist {
    }                    <==================(*) added incorrectly
        devnode "^(ram|raw|loop|fd|md|dm-|sr|scd|st)[0-9]*"
        devnode "^hd[a-z]"
    }
    
    blacklist {          <==================(*) Changed to blacklist from blacklist_exceptions
    }                    <==================(*) added incorrectly
        device {
            product "XXXX"
            vendor "XXXX"
        }
    }
    

Environment

  • Red Hat OpenStack Platform 16.2

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content