Bug 1807814

Summary:	[RFE]Provide option to control blacklist or whitelist multipath devices from gluster-ansible roles
Product:	[Red Hat Storage] Red Hat Gluster Storage	Reporter:	Gobinda Das <godas>
Component:	gluster-ansible	Assignee:	Gobinda Das <godas>
Status:	CLOSED ERRATA	QA Contact:	SATHEESARAN <sasundar>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	rhhiv-1.8	CC:	asakthiv, pprakash, rcyriac, rhs-bugs, sabose, sasundar
Target Milestone:	---	Keywords:	ZStream
Target Release:	RHGS 3.5.z Batch Update 2
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	gluster-ansible-infra-1.0.4-7.el8rhgs	Doc Type:	Enhancement
Doc Text:	Previously, Ansible roles were not supported to blacklist or whitelist multipath devices. In this release, Ansible roles are added to support the user to blacklist or whitelist multipath devices for Red Hat Hyperconverged Infrastructure for Virtualization deployments.	Story Points:	---
Clone Of:	1807808	Environment:	rhhiv, rhel8
Last Closed:	2020-06-16 05:57:29 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	1807815
Bug Blocks:	1807808

Description Gobinda Das 2020-02-27 10:03:30 UTC

Description of problem:
  From cockpit based deployment now we don't have any option to blacklist multipath device, user has to manually blacklist. From cockpit UI user should choose whether to disable or enable mutipath devices.

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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 6 SATHEESARAN 2020-04-07 09:00:59 UTC

Tested with gluster-ansible-infra-1.0.4-7.el8rhgs

Adding 'blacklist_mpath_devices' to the inventory  with the required disks, then those disks are blacklisted

blacklist_mpath_devices:
  - sdb
  - sdc

Comment 11 errata-xmlrpc 2020-06-16 05:57:29 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-2020:2575