Bug 1896164 - [Docs][RFE] Document using LVM on a cinder volume exposes the data to the compute host
Summary: [Docs][RFE] Document using LVM on a cinder volume exposes the data to the com...
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: documentation
Version: 16.1 (Train)
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: ---
Assignee: RHOS Documentation Team
QA Contact: RHOS Documentation Team
URL:
Whiteboard:
Depends On: 1261083
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-11-09 21:01 UTC by Andy Stillman
Modified: 2021-01-18 13:38 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-01-18 13:38:32 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHOSPDOC-16 0 High Open Cinder. Using LVM on a cinder volume exposes the data to the compute host 2020-12-08 11:29:59 UTC

Description Andy Stillman 2020-11-09 21:01:01 UTC
Description of problem: Need to hide the logical volumes (LVs) created by the openstack guests to the operators working on the baremetal node where the guests are hosted.


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


How reproducible: 
Every time

1. Create a new cinder volume and present it to an instance
2. Use LVM against the raw device (pvcreate/vgcreate/lvcreate)
3. Run 'lvs -o +devices' on the compute

Actual results:
LVM from the guest is seen on the host

Expected results:
host should not be able to see LVM from the guest

Additional info:
This can cause problems such as conflicting VG names on the compute. It can also cause the LVM on the compute to adjust metadata that the instance is not aware of, leading to things like missing volumes.

Current workaround is to set a filter on the compute node.

Comment 3 ndeevy 2021-01-18 13:38:32 UTC
Closing this BZ to track via: https://issues.redhat.com/browse/RHOSPDOC-16


Note You need to log in before you can comment on or make changes to this bug.