Using LVM on a cinder volume on the instance causes the compute node to pick up the LVM at the host level
Bug #1855704 reported by
Giulio Fidente
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tripleo |
Fix Released
|
Medium
|
Giulio Fidente |
Bug Description
Using LVM on a cinder volume on the instance causes the compute node to pick up the LVM at the host level
To reproduce:
1. Create a new cinder volume and present it to an instance
2. Use LVM against the raw device (pvcreate/
3. Run 'lvs -o +devices' on the compute
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.
Changed in tripleo: | |
milestone: | ussuri-1 → ussuri-2 |
Changed in tripleo: | |
milestone: | ussuri-2 → ussuri-3 |
Changed in tripleo: | |
milestone: | ussuri-3 → ussuri-rc3 |
Changed in tripleo: | |
milestone: | ussuri-rc3 → victoria-1 |
Changed in tripleo: | |
milestone: | victoria-1 → victoria-3 |
To post a comment you must log in.
Fix proposed to branch: master /review. opendev. org/697990
Review: https:/