[LVMiSCSI] A volume is deleted unexpectedly during volume migration when src and dst VG names are same
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Cinder |
Fix Released
|
Undecided
|
Mitsuhiro Tanino |
Bug Description
When using LVMISCSIDriver, a volume is unexpectedly deleted during volume migration operation.
This problem only occurs when the volume_group of backend A and backend B is same value by misconfiguration.
Even if the configuration is wrong, cinder should not delete the volume unexpectedly for user.
----- cinder.conf
enabled_
[LVM_iscsi_drv]
volume_
volume_
volume_
[LVM_iscsi_drv2]
volume_
volume_
volume_
-----
Recreation Steps
(1) Configure multiple LVMiSCSI backend using same VG
(2) Create a new volume
(3) Migrate the volume to other backend
Logs
$ cinder-manage host list
control.com nova
control.
control.
$ sudo lvs
$ cinder create --name iscsi1 --volume-type LVM_iscsi 1
....
$ cinder list
+------
| ID | Status | Name | Size | Volume Type | Bootable | Attached to |
+------
| a57240ea-
+------
$ sudo lvs
LV VG Attr LSize Pool Origin Data% Move Log Cpy%Sync Convert
volume-
$ cinder migrate a57240ea-
$ sudo lvs
$ sudo lvs
Whole c-vol log is here.
http://
Changed in cinder: | |
assignee: | nobody → Mitsuhiro Tanino (mitsuhiro-tanino) |
Changed in cinder: | |
milestone: | none → kilo-2 |
status: | Fix Committed → Fix Released |
Changed in cinder: | |
milestone: | kilo-2 → 2015.1.0 |
Fix proposed to branch: master /review. openstack. org/142922
Review: https:/