Corey Bryant 4558b60864 Only include LVM loop device in LVM global_filter ... The following tempest test is failing regularly in the gate: tempest.api.compute.volumes.test_attach_volume.AttachVolumeTestJSON.test_list_get_volume_attachments The theory behind this fix is that tests are creating/deleting /dev/sdX devices and LVM ends up attempting to open an already removed device which causes LVM to temporarily block. Setting the global_filter will limit the block devices that are used by LVM system components. This adds a new config option config.cinder.loop-device. In not set the loop device will be generated. Closes-Bug: #1918306 Change-Id: I8cccf7a1b1af2e15106b11023652af23c7715e6f		2021-03-11 19:57:10 -05:00
..
bin	Only include LVM loop device in LVM global_filter	2021-03-11 19:57:10 -05:00
data	Moved from database dump to hack.	2019-04-10 14:12:01 -04:00
etc	Rework the test framework & the clustering test	2021-01-15 15:58:03 +03:00
images	Clustering prototype	2019-11-04 13:03:41 +00:00
lib/python3.8/site-packages/openstack_dashboard/themes/ubuntu	Use focal/core20/Ussuri/OVN & enable confinement	2020-09-25 13:20:12 +00:00
templates	Only include LVM loop device in LVM global_filter	2021-03-11 19:57:10 -05:00
snap-openstack.yaml	Only include LVM loop device in LVM global_filter	2021-03-11 19:57:10 -05:00