Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1953921

Summary: "clean existing gluster deployment" doesn't remove filter from lvm.conf
Product: [oVirt] cockpit-ovirt Reporter: Sandro Bonazzola <sbonazzo>
Component: GenericAssignee: Gobinda Das <godas>
Status: CLOSED NOTABUG QA Contact: SATHEESARAN <sasundar>
Severity: medium Docs Contact:
Priority: unspecified    
Version: ---CC: arachman, bugs, cshao
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
: 1971451 (view as bug list) Environment:
Last Closed: 2021-06-22 10:19:19 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Gluster RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1971451    
Bug Blocks:    

Description Sandro Bonazzola 2021-04-27 08:03:52 UTC 
initially reported on https://github.com/oVirt/cockpit-ovirt/issues/8 by Derek P. Moore (https://github.com/derekm)

"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."

"This blog accelerated my ability to fix this situation: https://blog.wefixit.at/ovirt-node-4-4-gluster-installation-failed-with-device-dev-sdb-excluded-by-a-filter/"
Comment 1 SATHEESARAN 2021-05-18 05:24:19 UTC 
During the gluster deployment, the playbook does removes the LVM filter and towards the end of deployment
the playbook regenerates the LVM filter using 'vdsm-tool config-lvm-filter -y'.

If something fails during gluster deployment, there shouldn't be any LVM filter entries, as that was removed
in the failer earlier attempt.

I will particularly try to induce the failure during the deployment and then will try to reproduce this issue
Comment 2 SATHEESARAN 2021-06-22 10:19:19 UTC 
As mentioned in comment1, the gluster deployment takes care of cleaning the pre-existing LVM filter, proceed to gluster deployment,
then regenerates the LVM filter. This cleanup procedure doesn't required to fix anything related to LVM filter as the redeployment cleans
the pre-existing filter as the first task.

Closing this bug. If the issue is seen again, please provide the required logs and results from ansible playbook execution