cinder-volume fails to initialize properly
| Affects | Status | Importance | Assigned to | Milestone | ||
|---|---|---|---|---|---|---|
| Mirantis OpenStack | Status tracked in 10.0.x | |||||
| 10.0.x |
Invalid
|
High
|
Eugene Nikanorov | |||
| 7.0.x |
Invalid
|
High
|
MOS Maintenance | |||
| 8.0.x |
Invalid
|
High
|
MOS Maintenance | |||
| 9.x |
Invalid
|
High
|
Eugene Nikanorov | |||
Bug Description
The following output from pvs command prevents cinder-volume with LVM driver to initialize properly.
A stack trace could be seen on cinder-volume startup and on any create-volume operation.
root@node-33:~# pvs --noheadings --unit=g
Couldn't find device with uuid fZPJvz-
/dev/sda3 cinder lvm2 a-- 2793.91g 2528.91g
/dev/sdb3 cinder lvm2 a-- 2793.91g 2793.91g
/dev/sdc3 cinder lvm2 a-- 2793.91g 2793.91g
/dev/sdd3 cinder lvm2 a-- 2793.91g 2793.91g
/dev/sde4 os lvm2 a-- 222.96g 0.00g
unknown device cinder lvm2 a-m 11175.26g 11175.26g
The problem could be worked around by running:
vgreduce --clearmissing cinder
Expected result:
On driver initialization failure cinder-volume should exit to clearly indicate that it is not operational.
| Eugene Nikanorov (enikanorov) wrote | #1 |
| Changed in mos: | |
| assignee: | nobody → MOS Cinder (mos-cinder) |
| tags: | added: need-info |
| tags: | removed: need-info |
| tags: | added: need-info |
| Ivan Kolodyazhny (e0ne) wrote | #4 |
| Eugene Nikanorov (enikanorov) wrote | #5 |
| Ivan Kolodyazhny (e0ne) wrote | #6 |
This was discovered on MOS 7 (Kilo), but the LVM driver code is the same in 8, 9 and in upstream cinder, so it makes sense to file it upstream as well.