Looks like a Nova problem. We need the logs from this, but my assumption is the Cinder volume is indeed attached and therefore in-use, so Cinder is working as expected.
I am not sure if the expectation on the Nova side is that they fully rollback and clean up the Cinder volume in case of a failure like this, or if it is kept around as a means to troubleshoot what happened. ** Also affects: nova Importance: Undecided Status: New ** Changed in: cinder Status: New => Incomplete -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1745149 Title: encrypted volume is in "in-use" state while boot from volume failed Status in Cinder: Incomplete Status in OpenStack Compute (nova): New Bug description: Description of problem: A bootable volume that is encrypted is created and encryption was not configured in nova. create new server failed but the volume status stay in "in-use" state. (openstack) server list +--------------------------------------+-------+--------+-----------------------------------+--------+--------+ | ID | Name | Status | Networks | Image | Flavor | +--------------------------------------+-------+--------+-----------------------------------+--------+--------+ | ea85b1a0-4bc7-40ec-ae4b-19e3a1095a4f | inst2 | ERROR | | | tiny | | 450255af-5341-4626-b5ef-17de749137ad | inst1 | ACTIVE | internal=192.168.0.11, 10.0.0.216 | cirros | tiny | +--------------------------------------+-------+--------+-----------------------------------+--------+--------+ (openstack) (openstack) (openstack) volume list +--------------------------------------+-------------+-----------+------+--------------------------------+ | ID | Name | Status | Size | Attached to | +--------------------------------------+-------------+-----------+------+--------------------------------+ | bb12b367-e4e1-471a-a0b9-86b7f32be740 | encrypt_vol | in-use | 1 | Attached to inst2 on /dev/vda | | 5c8ff52c-d7e4-4c1f-9104-b6a780539340 | vol1 | available | 1 | | +--------------------------------------+-------------+-----------+------+--------------------------------+ Version-Release number of selected component (if applicable): puppet-cinder-11.3.0-2.el7ost.noarch python-cinder-11.0.1-2.el7ost.noarch python-cinderclient-3.1.0-1.el7ost.noarch openstack-cinder-11.0.1-2.el7ost.noarch openstack-nova-console-16.0.2-8.el7ost.noarch python-novaclient-9.1.1-1.el7ost.noarch openstack-nova-compute-16.0.2-8.el7ost.noarch openstack-nova-scheduler-16.0.2-8.el7ost.noarch openstack-nova-api-16.0.2-8.el7ost.noarch puppet-nova-11.4.0-2.el7ost.noarch openstack-nova-common-16.0.2-8.el7ost.noarch openstack-nova-placement-api-16.0.2-8.el7ost.noarch openstack-nova-conductor-16.0.2-8.el7ost.noarch python-nova-16.0.2-8.el7ost.noarch openstack-nova-migration-16.0.2-8.el7ost.noarch openstack-nova-novncproxy-16.0.2-8.el7ost.noarch How reproducible: 100% Steps to Reproduce: 1. Configure encryption in Cinder but not in nova 2. Create bootable volume from image 3. Create server from volume Actual results: Server create failed but volume status is "in-use" Expected results: Server create failed but volume status is "available" To manage notifications about this bug go to: https://bugs.launchpad.net/cinder/+bug/1745149/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp