Bug 1524500 - [downstream clone - 4.1.9] Guest LVs created on raw volumes are auto activated on the hypervisor with FC storage (lvm filter?)
Summary: [downstream clone - 4.1.9] Guest LVs created on raw volumes are auto activate...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: vdsm
Version: 4.1.0
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ovirt-4.1.9
: ---
Assignee: Nir Soffer
QA Contact: Kevin Alon Goldblatt
URL:
Whiteboard:
Depends On: 1449968 1523152
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-12-11 15:51 UTC by Tal Nisan
Modified: 2021-09-09 12:56 UTC (History)
27 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Currently, LVM scans and activates raw volumes during boot. Then it scans and activates guest logical volumes created inside a guest on top of the raw volumes. It also scans and activates guest logical volumes inside LUNs which are not part of a Red Hat Virtualization storage domain. As a result, there may be thousands of active logical volumes on a host, which should not be active. This leads to very slow boot time and may lead to data corruption later if a logical volume active on the host was extended on another host. To avoid this, you can configure an LVM filter using the "vdsm-tool config-lvm-filter" command. The LVM filter prevents scanning and activation of logical volumes not required by the host, which improves boot time.
Clone Of: 1523152
Environment:
Last Closed: 2018-01-24 14:44:27 UTC
oVirt Team: Storage
Target Upstream Version:
Embargoed:
lsvaty: testing_plan_complete-

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2018:0136 0 normal SHIPPED_LIVE VDSM bug fix and enhancement update 4.1.9 2018-01-24 19:39:10 UTC
oVirt gerrit 83524 0 None None None 2017-12-11 15:51:25 UTC
oVirt gerrit 84396 0 None None None 2017-12-11 15:51:25 UTC
oVirt gerrit 84694 0 None None None 2017-12-11 15:51:25 UTC
oVirt gerrit 84695 0 None None None 2017-12-11 15:51:25 UTC
oVirt gerrit 84826 0 None None None 2017-12-11 15:51:25 UTC
oVirt gerrit 84829 0 None None None 2017-12-11 15:51:25 UTC
oVirt gerrit 84918 0 ovirt-4.1 MERGED lvmfilter: Introduce the storage.lvmfilter module 2017-12-11 16:33:19 UTC
oVirt gerrit 84919 0 ovirt-4.1 MERGED tool: Add config-lvm-filter command 2017-12-11 16:47:58 UTC
oVirt gerrit 84920 0 ovirt-4.1 MERGED spec: Require python-augeas 2017-12-11 17:36:10 UTC
oVirt gerrit 84921 0 ovirt-4.1 MERGED lvmconf: Introduce the storage lvmconf module 2017-12-11 18:04:52 UTC
oVirt gerrit 84922 0 ovirt-4.1 MERGED lvmfilter: Analyze current LVM filter 2017-12-12 08:49:53 UTC
oVirt gerrit 84923 0 ovirt-4.1 MERGED config-lvm-filter: Configure LVM filter 2017-12-12 09:10:13 UTC
oVirt gerrit 85126 0 None None None 2017-12-11 15:51:25 UTC
oVirt gerrit 85127 0 None None None 2017-12-11 15:51:25 UTC
oVirt gerrit 85233 0 None None None 2017-12-11 15:51:25 UTC
oVirt gerrit 85234 0 ovirt-4.1 MERGED storaqge: fix failing lvmfilter test 2017-12-12 09:19:02 UTC
oVirt gerrit 85235 0 ovirt-4.1 MERGED lvmfilter: Remove double [yes/No]? 2017-12-12 11:01:53 UTC
oVirt gerrit 85236 0 ovirt-4.1 MERGED lvmfilter: Filter out the master LV on the SPM 2017-12-17 07:52:19 UTC

Comment 2 Nir Soffer 2018-01-10 14:59:19 UTC 
The patches were merged on Dec 17, not sure why gerrit did not update the bug.
Comment 4 Kevin Alon Goldblatt 2018-01-23 14:23:01 UTC 
Verified with the following code:
----------------------------------------
ovirt-engine-4.1.9.1-0.1.el7.noarch
vdsm-4.19.45-1.el7ev.x86_64


Verified with the following scenario:
----------------------------------------
Steps to Reproduce:
1.install host and add it to manager
2.add fc storage to datacenter
3.create vm on raw device with lvm on top of it
4.shutdown the vm, put host into maintenance
6, reboot the host


Before filter output:
---------------------------------------
lvs -o vg_name,lv_name,devices,attr
  VG                                   LV                                   Devices                                                                           Attr      
  7ae6a9e0-f021-4e9f-85de-fc14082516ae 0643ff20-a35d-4a5c-811e-a712d47d6de8 /dev/mapper/3514f0c5a51601382(39)                                                 -wi-ao----
  7ae6a9e0-f021-4e9f-85de-fc14082516ae ids                                  /dev/mapper/3514f0c5a51601382(29)                                                 -wi-a-----
  7ae6a9e0-f021-4e9f-85de-fc14082516ae inbox                                /dev/mapper/3514f0c5a51601382(30)                                                 -wi-a-----
  7ae6a9e0-f021-4e9f-85de-fc14082516ae metadata                             /dev/mapper/3514f0c5a51601382(0)                                                  -wi-a-----
  7ae6a9e0-f021-4e9f-85de-fc14082516ae xleases                              /dev/mapper/3514f0c5a51601382(5)                                                  -wi-a-----
  VolGroup01                           root                                 /dev/sde3(0)                                                                      -wi-ao----
  vg1                                  lvol0                                /dev/7ae6a9e0-f021-4e9f-85de-fc14082516ae/0643ff20-a35d-4a5c-811e-a712d47d6de8(0) -wi-a-----
  vg2                                  lvol0                                /dev/mapper/3514f0c5a51601381(0)                                                  -wi-------


Output after adding output:
------------------------------------
VolGroup01     root        /dev/sde3(0)   -wi-ao----


Moving to VERIFIED
Comment 7 errata-xmlrpc 2018-01-24 14:44:27 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHEA-2018:0136
Comment 8 Franta Kust 2019-05-16 12:54:47 UTC 
BZ<2>Jira re-sync
Comment 9 Daniel Gur 2019-08-28 13:13:55 UTC 
sync2jira
Comment 10 Daniel Gur 2019-08-28 13:18:09 UTC 
sync2jira
Note You need to log in before you can comment on or make changes to this bug.