remove_export after changing volume to available
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Cinder |
Fix Released
|
Undecided
|
Lisa Li |
Bug Description
In master branch with lvm as backend storage:
During detach_volume, Cinder at first sets volume in available status and then removes iscsi targets.
set volume in available: https:/
remove export: https:/
This leads following problem:
1. Attach volume to instance 1.
2. Detach volume from instance 1.
3. At the time (when volume becomes available, and before removing remove_export) attach the volume to instance 2.
4. Is is possible that when isci target is created for instance 2, but remove_export for instance 1 removes the just created iscsi target.
As a result, attach volume to intance 2 fails.
This ever leaded CI fails http://
This exists in LVM, I am not sure whether other backend storages have same problem.
Fix proposed to branch: master /review. openstack. org/360211
Review: https:/