Bug 1971451

Summary:	"clean existing gluster deployment" doesn't remove filter from lvm.conf
Product:	[Red Hat Storage] Red Hat Gluster Storage	Reporter:	SATHEESARAN <sasundar>
Component:	rhhi	Assignee:	Gobinda Das <godas>
Status:	CLOSED NOTABUG	QA Contact:	SATHEESARAN <sasundar>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	rhhiv-1.8	CC:	arachman, bugs, cshao, godas, rhs-bugs, sbonazzo
Target Milestone:	---	Keywords:	ZStream
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:	1953921
Clones:	1971452 (view as bug list)		Environment:
Last Closed:	2021-06-22 09:58: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:	1971452
Bug Blocks:	1953921

Description SATHEESARAN 2021-06-14 06:22:55 UTC

Description
------------
"After cleaning up a gluster deployment that has gone awry, you cannot recreate the same gluster deployment without deleting filter= lines from /etc/lvm/lvm.conf on all nodes."

Expected Result:
---------------
The playbook for cleaning gluster deployment should remove /etc/lvm/lvm.conf file before cleanup and regenerate file post cleanup is completed

Comment 2 SATHEESARAN 2021-06-22 09:58:29 UTC

This community user reported issue doesn't affect RHHI-V deployment.
RHHI-V deployment always cleans up the LVM filter as the very first step of deployment,
and regenerates the filter towards the close of gluster deployment.

Cleanup doesn't touch fixing LVM filters as the deployment takes care of cleaning all the
pre-existing filters and regenerating them post creation of bricks.

Closing this bug as there is no harm in not fixing LVM filter in cleanup procedure