Bug 1627103 - [downstream clone - 4.2.7] Blacklist multipath for local devices related to HCI Gluster only (allow all other shared storage protocols, like sas)
Summary: [downstream clone - 4.2.7] Blacklist multipath for local devices related to H...
Keywords:
Status: CLOSED CANTFIX
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: vdsm
Version: unspecified
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ovirt-4.2.8
: ---
Assignee: Vojtech Juranek
QA Contact: Elad
URL:
Whiteboard:
Depends On: 1625557
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-09-10 12:59 UTC by RHV bug bot
Modified: 2019-04-28 10:38 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1625557
Environment:
Last Closed: 2018-12-10 14:13:26 UTC
oVirt Team: Storage
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 94168 0 master ABANDONED multipath: Blacklist "sas" local devices 2018-10-11 12:24:26 UTC
oVirt gerrit 95981 0 ovirt-4.2 ABANDONED multipath: Blacklist obsolete and local devices 2018-12-06 14:11:41 UTC

Description RHV bug bot 2018-09-10 12:59:53 UTC 
+++ This bug is an upstream to downstream clone. The original bug is: +++
+++   bug 1625557 +++
======================================================================

Description of problem:
The fix for bug 1016535 added support to blacklist fcp and iscsi devices. The introduced a regression for sas devices.

Version-Release number of selected component (if applicable):
4.20.39

(Originally by Ala Hino)
Comment 5 Vojtech Juranek 2018-12-04 13:16:48 UTC 
We tried to come up with a general blacklist which won't break any existing setup. However, it turned out that such blacklist has to be very less restrictive than we originally expected, so it probably won't (fully) solve this issue or any of the related issues. Main purpose of proposed patch is to add documentation so that admins can easily adjust blacklists to their needs according to their specific setups.
Comment 6 Tal Nisan 2018-12-10 14:13:26 UTC 
We cannot fix this for 4.2.8 according to comment #5, closing.
Note You need to log in before you can comment on or make changes to this bug.