My Fedora 19 environment does this as well. Invalid volume_group specified in cinder.conf -> create a volume -> stays in "creating" state. Calling "force-delete" then results in the volume staying in the "deleting" state.
My Fedora 19 environment does this as well. Invalid volume_group specified in cinder.conf -> create a volume -> stays in "creating" state. Calling "force-delete" then results in the volume staying in the "deleting" state.