libvirt does not store connection_info after BFV setup
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
Medium
|
Dan Smith | ||
Havana |
Fix Released
|
Medium
|
Dan Smith | ||
Icehouse |
Fix Released
|
Medium
|
Dan Smith |
Bug Description
If booting from a volume, the virt driver does the setup of the volume with cinder before starting the instance. This differs from the attach volume case, which is managed by nova itself. Since the connect operation could yield new details in the connection_info structure that need to be persisted until teardown time, it is important that the connection_info be written back after connect completes. Nova's attach_volume() does this, but libvirt does not. Specifically in the case of the fibre channel code, this means we don't persist information about multipath devices which means we don't fully tear down everything at disconnect time.
This is present in at least Havana, and I expect it is present in Icehosue and master as well.
tags: | removed: in-stable-havana |
Changed in nova: | |
status: | Confirmed → Fix Committed |
Changed in nova: | |
milestone: | none → juno-2 |
status: | Fix Committed → Fix Released |
Changed in nova: | |
milestone: | juno-2 → 2014.2 |
Related fix proposed to branch: stable/havana /review. openstack. org/98874
Review: https:/