Forget to change volume's status when an error occurs in swap volume
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
Undecided
|
Vladik Romanovsky |
Bug Description
If the blockrebase(swap volume) fails, the status of the attached volume remains of detaching.
Tried Commit ID:b03799398422
1.Before Swap Volume
$ cinder list
+------
| ID | Status | Display Name | Size | Volume Type | Bootable | Attached to |
+------
| 66230802-
| c3d51a52-
+------
2.Swap volume running
$ cinder list
+------
| ID | Status | Display Name | Size | Volume Type | Bootable | Attached to |
+------
| 66230802-
| c3d51a52-
+------
3.An error occurs in swap volume
For example, cancel a blockrebase job.
libvirtError: virDomainGetBlo
4.After an error occurs
$ cinder list
+------
| ID | Status | Display Name | Size | Volume Type | Bootable | Attached to |
+------
| 66230802-
| c3d51a52-
+------
tags: | added: volumes |
Changed in nova: | |
assignee: | nobody → Vladik Romanovsky (vladik-romanovsky) |
Changed in nova: | |
milestone: | none → icehouse-3 |
Changed in nova: | |
status: | Fix Committed → Fix Released |
Changed in nova: | |
milestone: | icehouse-3 → 2014.1 |
Fix proposed to branch: master /review. openstack. org/49395
Review: https:/