Comment 11 for bug 1053931

Hi,

I can confirm that in havana happens again. I tried to spawn machine from a volume snapshot with the option create new volume. First interesting thing is that cinder-scheduler chose to create the corresponding volume on the agent that was down although there were other cinder-volume agents up. So the status of the volume is stuck in creating:
 cinder list
+--------------------------------------+----------------+------------------+------+-------------+----------+--------------------------------------+
| ID | Status | Display Name | Size | Volume Type | Bootable | Attached to |
+--------------------------------------+----------------+------------------+------+-------------+----------+--------------------------------------+
| 0c7332a2-4ddd-413c-828b-3ba93b2f98da | in-use | bla_ubuntu | 10 | None | false | 55840e8b-7cc8-43ea-b8c0-bfcdf82c769d |
| 20e0debb-55b8-4bde-9395-2e4179559536 | available | debian73 | 10 | None | false | |
| 46b9846c-c8ad-4847-a6b9-e8bc086b41b0 | available | ubuntu1204 | 10 | None | false | |
| 62b58aff-ce6e-4b7f-883e-589103ecaa87 | in-use | bla_00 | 100 | None | false | 55840e8b-7cc8-43ea-b8c0-bfcdf82c769d |
| 9a68af42-e73f-4fb7-8f87-621b2b4375f4 | error_deleting | ssdf | 1 | None | false | |
| a7728dbf-3752-438a-9395-f14efad98ccf | available | ubuntu1204_unity | 10 | None | false | |
| e9247a44-cb65-4164-8fa2-9c2433949278 | creating | | 10 | None | false | |
+--------------------------------------+----------------+------------------+------+-------------+----------+--------------------------------------+