Steps to reproduce
---
1) Run rally scenario create-and-attach-volume:
root@4d26aea48680:/# rally -v task start create-and-attach-volume.json --tag create-and-attach-volume
2) See in /var/log/cinder-all.log "Cannot delete volume <volume_id>: volume is busy":
...
<158>Oct 7 05:29:00 node-6 cinder-volume 2015-10-07 05:29:00.115 16594 INFO cinder.volume.manager [req-6b46fd26-ad2f-42ed-9da5-02a47be922be 5fc88ee5f65d41f39f225c37c7644825 47fe3f9221d64b27ab03afe1625b4eab - - -] volume 4304a9ba-e5ab-4021-9ed4-93d81b88fe51: deleting
<156>Oct 7 05:29:00 node-6 cinder-volume 2015-10-07 05:29:00.212 16594 WARNING cinder.volume.drivers.rbd [req-6b46fd26-ad2f-42ed-9da5-02a47be922be 5fc88ee5f65d41f39f225c37c7644825 47fe3f9221d64b27ab03afe1625b4eab - - -] ImageBusy error raised while deleting rbd volume. This may have been caused by a connection from a client that has crashed and, if so, may be resolved by retrying the delete after 30 seconds has elapsed.
<155>Oct 7 05:29:00 node-6 cinder-volume 2015-10-07 05:29:00.217 16594 ERROR cinder.volume.manager [req-6b46fd26-ad2f-42ed-9da5-02a47be922be 5fc88ee5f65d41f39f225c37c7644825 47fe3f9221d64b27ab03afe1625b4eab - - -] Cannot delete volume 4304a9ba-e5ab-4021-9ed4-93d81b88fe51: volume is busy
Verified on version: "2015.1.0-7.0"
----------------
VERSION:
feature_groups:
- mirantis
production: "docker"
release: "7.0"
openstack_
api: "1.0"
build_number: "
----------------
Steps to reproduce and-attach- volume: 80:/# rally -v task start create- and-attach- volume. json --tag create- and-attach- volume
---
1) Run rally scenario create-
root@4d26aea486
2) See in /var/log/ cinder- all.log "Cannot delete volume <volume_id>: volume is busy": volume. manager [req-6b46fd26- ad2f-42ed- 9da5-02a47be922 be 5fc88ee5f65d41f 39f225c37c76448 25 47fe3f9221d64b2 7ab03afe1625b4e ab - - -] volume 4304a9ba- e5ab-4021- 9ed4-93d81b88fe 51: deleting volume. drivers. rbd [req-6b46fd26- ad2f-42ed- 9da5-02a47be922 be 5fc88ee5f65d41f 39f225c37c76448 25 47fe3f9221d64b2 7ab03afe1625b4e ab - - -] ImageBusy error raised while deleting rbd volume. This may have been caused by a connection from a client that has crashed and, if so, may be resolved by retrying the delete after 30 seconds has elapsed. volume. manager [req-6b46fd26- ad2f-42ed- 9da5-02a47be922 be 5fc88ee5f65d41f 39f225c37c76448 25 47fe3f9221d64b2 7ab03afe1625b4e ab - - -] Cannot delete volume 4304a9ba- e5ab-4021- 9ed4-93d81b88fe 51: volume is busy
...
<158>Oct 7 05:29:00 node-6 cinder-volume 2015-10-07 05:29:00.115 16594 INFO cinder.
<156>Oct 7 05:29:00 node-6 cinder-volume 2015-10-07 05:29:00.212 16594 WARNING cinder.
<155>Oct 7 05:29:00 node-6 cinder-volume 2015-10-07 05:29:00.217 16594 ERROR cinder.