Using LVM on a cinder volume exposes the data to the host

Solution Verified - Updated -

Issue

The following issues may appear on the computes or the controllers in the environment

  • LVM appears to be see volume groups from my guests
  • LVM is reporting that there are duplicate volume group names
  • Volume detachments fail because LVM is accessing the storage
  • My guests fail to boot due to problems with LVM
  • The LVM on my guest machine is in a partial state due to a missing disk that actually exists
  • Cinder actions fail on devices that have LVM built on them
  • Cinder snapshots fail to remove correctly
Nov 22 16:22:52 overcloud-volume01 cinder-volume[28404]: Stdout: u"Unexpected error while running command.\nCommand: sudo cinder-rootwrap /etc/cinder/rootwrap.conf lvremove --config activation { retry_deactivation = 1} devices { ignore_suspended_devices = 1} -f cinder-volumes/_snapshot-<UUID>\nExit code: 5\nStdout: u''\nStderr: u'File descriptor 7 (/dev/urandom) leaked on lvremove invocation. Parent PID 39750: /usr/bin/python2\\n  Logical volume cinder-volumes/_snapshot-<UUID> is used by another device.\\n'"

Environment

  • Red Hat Openstack Platform
  • LVM configured on the volumes attached to instances
  • Non-LVM cinder backend

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In