libvirt: if exception raised during volume_detach, volume state is inconsistent
Bug #1057756 reported by
Vish Ishaya
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
Medium
|
Vish Ishaya | ||
Folsom |
Fix Released
|
Medium
|
Vish Ishaya | ||
nova (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Quantal |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
Currently the libvirt code will always logout of the iscsi target
during detach error, but the exception will cause the volume to
remain in an attached state. This needs to be more consistent.
Related branches
lp://staging/~gandelman-a/ubuntu/quantal/nova/2012.2.1
- Openstack Ubuntu Testers: Pending requested
-
Diff: 121 lines (+100/-4)1 file modifieddebian/changelog (+100/-4)
CVE References
summary: |
- libvirt: if instance is destroyed during detach, volume remains in - detached state + libvirt: if exception raised during voulume_detach, volume state is + inconsistent |
Changed in nova: | |
status: | New → In Progress |
assignee: | nobody → Vish Ishaya (vishvananda) |
description: | updated |
Changed in nova: | |
importance: | Undecided → Medium |
tags: | added: folsom-backport-potential |
Changed in nova: | |
milestone: | none → grizzly-1 |
status: | Fix Committed → Fix Released |
summary: |
- libvirt: if exception raised during voulume_detach, volume state is + libvirt: if exception raised during volume_detach, volume state is inconsistent |
tags: | removed: folsom-backport-potential |
Changed in nova (Ubuntu): | |
status: | New → Fix Released |
Changed in nova (Ubuntu Quantal): | |
status: | New → Confirmed |
Changed in nova: | |
milestone: | grizzly-1 → 2013.1 |
To post a comment you must log in.
Fix proposed to branch: master /review. openstack. org/13791
Review: https:/