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

Bug 1696634

Summary:	[RFE] run /usr/bin/vdsm-tool config-lvm-filter at installation time
Product:	Red Hat Enterprise Virtualization Manager	Reporter:	Daniele <dconsoli>
Component:	ovirt-engine	Assignee:	Tal Nisan <tnisan>
Status:	CLOSED DUPLICATE	QA Contact:	Lukas Svaty <lsvaty>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	4.4.0	CC:	dougsland, lsurette, mkalinin, nsoffer, srevivo, tnisan, vjuranek
Target Milestone:	---	Keywords:	FutureFeature
Target Release:	---	Flags:	lsvaty: testing_plan_complete-
Hardware:	All
OS:	All
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-06-15 14:56:23 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	Storage	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Daniele 2019-04-05 10:28:52 UTC

Description of problem:
/usr/bin/vdsm-tool config-lvm-filter should be run at installation time. The configuration it produces seems to be sane and prevents issues like having the host occasionally see some VM's VG, which leads to issues.

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


How reproducible:
100%

Steps to Reproduce:
1. Install RHV-H
2. Check LVM filter
3. Run /usr/bin/vdsm-tool config-lvm-filter
4. The configuration generated is different from the default

Actual results:
LVM filter on hosts missing or different from the one generated by /usr/bin/vdsm-tool config-lvm-filter

Expected results:
LVM filter on hosts present and generated by /usr/bin/vdsm-tool config-lvm-filter

Additional info:
Example of issue caused by missing LVM filter: 02146286

Comment 1 Sandro Bonazzola 2019-04-05 11:37:35 UTC

Assigned to storage team for checking the issue.
I can't see the command being called during host deployment neither in ovirt-host-deploy nor in ansible host-deploy code or in vdsm %post section.
I think this call can either go into ovirt-host-deploy or in ansible host-deploy but I'd like storage team to understand why this is needed and how we missed to call it up to now.

Comment 2 Tal Nisan 2019-04-07 12:47:37 UTC

Nir / Vojtech, what's our take here?

Comment 3 Vojtech Juranek 2019-04-08 08:15:03 UTC

lvm filter is not run automatically during the installation and has to be run manually by the user which needs to either confirm proposed filter (in case no filter is configured) or edit the filter manually (in case filter is configured but different from what vdsm proposed). As for the reason why not to run it automatically, I'd defer to Nir, but I guess it's because it can cause serious issues if filter is not configured correctly, so admin review of the filter it required. Second, minor issue, could be, that IIRC imgbased run vdsm config after reboot and to verify lvm filter another reboot is needed, which would result into 2 reboots during install and bad user experience.

Comment 7 Sandro Bonazzola 2020-03-17 13:49:10 UTC

Moving to ovirt-engine since ovirt-host-deploy is not going to be shipped in 4.4.

Comment 9 Marina Kalinin 2020-05-01 22:33:37 UTC

Hi Daniele,

I propose to close this request as a duplicate of bz#1522926.
Please review and ack.

Comment 11 Tal Nisan 2020-06-15 14:56:23 UTC


*** This bug has been marked as a duplicate of bug 1522926 ***

Comment 14 Red Hat Bugzilla 2023-09-14 05:26:32 UTC

The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days