Bug 1433564 - update disable-multipath.sh script to enable multipath for specific device
Summary: update disable-multipath.sh script to enable multipath for specific device
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat Storage
Component: gdeploy
Version: rhgs-3.2
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
: RHGS 3.3.1 Async
Assignee: Sachidananda Urs
QA Contact: SATHEESARAN
URL:
Whiteboard:
Depends On:
Blocks: Gluster-HC-3 1581561
TreeView+ depends on / blocked
 
Reported: 2017-03-18 05:06 UTC by SATHEESARAN
Modified: 2018-06-21 03:34 UTC (History)
10 users (show)

Fixed In Version: gdeploy-2.0.2-20
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-06-21 03:33:14 UTC
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2018:1958 0 None None None 2018-06-21 03:34:47 UTC

Description SATHEESARAN 2017-03-18 05:06:00 UTC
Description of problem:
-----------------------
Grafton LA release had an requirement to disable multipath devices ( because of the bug 1303940 ) in the system. With that said, disable-multipath.sh script was developed to disable all the multipath devices.

With HCI GA, the bug 1303940 is fixed as use_lvmetad is set to '0', but still the vdsm configures multipath such that it creates the WWID/mpath names for the devices, even though such an device doesn't have multipath exist.
This is the behavior with any hypervisor managed in RHV.

So avoid WWID/mpath names getting assigned, we need to configure blacklisting of a device specifically.

Version-Release number of selected component (if applicable):
-------------------------------------------------------------
gdeploy-2.0.1-11.el7rhgs

How reproducible:
-----------------
Always

Steps to Reproduce:
-------------------
1. Run disable-multipath.sh script to blacklist the specific device

Actual results:
---------------
All the devices are blacklisted

Expected results:
-----------------
Blacklist the specific device

Comment 1 SATHEESARAN 2017-03-22 17:39:03 UTC
Also make sure that the file /etc/multipath.conf starts with these lines :

# VDSM REVISION 1.3
# VDSM PRIVATE

provided that these lines are not already there

Comment 5 Sachidananda Urs 2017-10-10 07:29:47 UTC
Commit: https://github.com/gluster/gdeploy/commit/40a0c02a46e should resolve the issue.

Comment 7 SATHEESARAN 2018-06-11 18:02:25 UTC
Tested with gdeploy-2.0.2-27.el7rhgs

/etc/multipath.conf file starts with these lines

# VDSM REVISION 1.3
# VDSM PRIVATE
# VDSM REVISION 1.5

In actual '# VDSM REVISION 1.3' is not required. vdsm revision value has been now bumped up to 1.5

Verified that all the devices are blacklisted.

Comment 9 errata-xmlrpc 2018-06-21 03:33:14 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHEA-2018:1958


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