Bug 1971452 - "clean existing gluster deployment" doesn't remove filter from lvm.conf
Summary: "clean existing gluster deployment" doesn't remove filter from lvm.conf
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat Storage
Component: gluster-ansible
Version: rhgs-3.5
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
: ---
Assignee: Gobinda Das
QA Contact: SATHEESARAN
URL:
Whiteboard:
Depends On:
Blocks: 1971451
TreeView+ depends on / blocked
 
Reported: 2021-06-14 06:25 UTC by SATHEESARAN
Modified: 2021-06-22 10:01 UTC (History)
10 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1971451
Environment:
Last Closed: 2021-06-22 10:01:12 UTC
Embargoed:

Attachments (Terms of Use)

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
Note You need to log in before you can comment on or make changes to this bug.