allow reset-state of multiple objects
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| python-cinderclient |
Fix Released
|
Wishlist
|
Eric Harney | ||
Bug Description
if we have a failure during an action we are running on multiple volumes we might have multiple volumes with state which we need to reset.
currently I can only run reset-state for a single object, but it would be helpful if we could do it for multiple objects (primarily if we currently volume state remains in error in case of a failure)
root@XXXX ~(keystone_admin)]# cinder list
+------
| ID | Status | Display Name | Size | Volume Type | Bootable | Attached to |
+------
| 1121404d-
| 2f2abeea-
| 990d2111-
| a6b9603d-
| ea526067-
+------
[root@XXXX ~(keystone_admin)]# cinder reset-state a6b9603d-
usage: cinder [--version] [--debug] [--os-username <auth-user-name>]
error: unrecognized arguments: ea526067-
Try 'cinder help ' for more information.
[root@XXXX ~(keystone_admin)]# cinder reset-state a6b9603d-
[root@XXXX ~(keystone_admin)]# cinder reset-state ea526067-
[root@XXXX ~(keystone_admin)]# cinder list
+------
| ID | Status | Display Name | Size | Volume Type | Bootable | Attached to |
+------
| 1121404d-
| 2f2abeea-
| 990d2111-
| a6b9603d-
| ea526067-
+------
| Changed in python-cinderclient: | |
| importance: | Undecided → Wishlist |
| Changed in python-cinderclient: | |
| assignee: | nobody → Eric Harney (eharney) |
| status: | New → In Progress |
| Changed in python-cinderclient: | |
| milestone: | none → 1.3.1 |
| status: | Fix Committed → Fix Released |

Reviewed: https:/ /review. openstack. org/59574 /git.openstack. org/cgit/ openstack/ python- cinderclient/ commit/ ?id=0e2bd33265d e840787a3d9e31f 7a14e83c44acf9
Committed: https:/
Submitter: Jenkins
Branch: master
commit 0e2bd33265de840 787a3d9e31f7a14 e83c44acf9
Author: Eric Harney <email address hidden>
Date: Mon Dec 2 18:05:54 2013 -0500
Reset-state and snapshot- reset-state for multiple objects
This allows a user to call reset-state or snapshot- reset-state on a
list of objects. The behavior is modeled after a similar change to
delete multiple volumes.
$ cinder reset-state good_volume good_volume_2
<no output>
Error behavior is as follows:
One success/one failure:
$ cinder reset-state good_volume asdf
Reset state for volume asdf failed: No volume with a name or ID of 'asdf' exists.
One failure:
$ cinder reset-state asdf
ERROR: Reset state for volume asdf failed: No volume with a name or ID of 'asdf' exists.
Two failures:
$ cinder reset-state asdf qwert
Reset state for volume asdf failed: No volume with a name or ID of 'asdf' exists.
Reset state for volume qwert failed: No volume with a name or ID of 'qwert' exists.
ERROR: Unable to reset the state for any of the specified volumes.
Related-Bug: 1241941 be0dac98ea04e47 08775250b7a
Closes-Bug: 1256069
Change-Id: Id0a36fb7de0d69