Bug 1971452

Summary: "clean existing gluster deployment" doesn't remove filter from lvm.conf
Product: [Red Hat Storage] Red Hat Gluster Storage Reporter: SATHEESARAN <sasundar>
Component: gluster-ansibleAssignee: Gobinda Das <godas>
Status: CLOSED NOTABUG QA Contact: SATHEESARAN <sasundar>
Severity: medium Docs Contact:
Priority: unspecified    
Version: rhgs-3.5CC: arachman, bugs, cshao, godas, pprakash, rcyriac, rhs-bugs, sabose, sasundar, sbonazzo
Target Milestone: ---   
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: 1971451 Environment:
Last Closed: 2021-06-22 10:01:12 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:    
Bug Blocks: 1971451    

Description SATHEESARAN 2021-06-14 06:25:59 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 1 Gobinda Das 2021-06-16 11:52:01 UTC 
Upstream PR: https://github.com/gluster/gluster-ansible/pull/132
Comment 2 SATHEESARAN 2021-06-22 10:01:12 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