Activity log for bug #1404867

Date Who What changed Old value New value Message
2014-12-22 12:17:06 Abhishek Kekane bug added bug
2014-12-22 12:17:49 Abhishek Kekane description If the instance is booted from volume and goes in to error state due to some reason. Volume from which instance is booted, remains in-use state even the instance is deleted. IMO, volume should be detached so that it can be used to boot other instance. Steps to reproduce: 1. Log in to Horizon, create a new volume. 2. Create an Instance using newly created volume. 3. Verify instance is in active state. $ source devstack/openrc demo demo $ nova list +--------------------------------------+------+--------+------------+-------------+------------------+ | ID | Name | Status | Task State | Power State | Networks | +--------------------------------------+------+--------+------------+-------------+------------------+ | dae3a13b-6aa8-4794-93cd-5ab7bf90f604 | nova | ACTIVE | - | Running | private=10.0.0.3 | +--------------------------------------+------+--------+------------+-------------+------------------+ Note: Use shelve-unshelve api to see the instance goes into error state. unshelving volume back instance does not work and sets instance state to error (ref: https://bugs.launchpad.net/nova/+bug/1404801) 4. Shelve the instance $ nova shelve <instance-uuid> 5. Verify the status is SHELVED_OFFLOADED. $ nova list +--------------------------------------+------+-------------------+------------+-------------+------------------+ | ID | Name | Status | Task State | Power State | Networks | +--------------------------------------+------+-------------------+------------+-------------+------------------+ | dae3a13b-6aa8-4794-93cd-5ab7bf90f604 | nova | SHELVED_OFFLOADED | - | Shutdown | private=10.0.0.3 | +--------------------------------------+------+-------------------+------------+-------------+------------------+ 6. Unshelve the instance. $ nova unshelve <instance-uuid> 5. Verify the instance is in Error state. $ nova list +--------------------------------------+------+-------------------+------------+-------------+------------------+ | ID | Name | Status | Task State | Power State | Networks | +--------------------------------------+------+-------------------+------------+-------------+------------------+ | dae3a13b-6aa8-4794-93cd-5ab7bf90f604 | nova | Error | unshelving | Spawning | private=10.0.0.3 | +--------------------------------------+------+-------------------+------------+-------------+------------------+ 6. Delete the instance using Horizon. 7. Verify that volume still in in-use state $ cinder list +--------------------------------------+--------+------+------+-------------+----------+--------------------------------------+ | ID | Status | Name | Size | Volume Type | Bootable | Attached to | +--------------------------------------+--------+------+------+-------------+----------+--------------------------------------+ | 4aeefd25-10aa-42c2-9a2d-1c89a95b4d4f | in-use | test | 1 | lvmdriver-1 | true | 8f7bdc24-1891-4bbb-8f0c-732b9cbecae7 | +--------------------------------------+--------+------+------+-------------+----------+--------------------------------------+ 8. In Horizon, volume "Attached To" information is displayed as "Attached to None on /dev/vda". 9. User is not able to delete this volume, or attached it to another instance as it is still in use. If the instance is booted from volume and goes in to error state due to some reason. Volume from which instance is booted, remains in-use state even the instance is deleted. IMO, volume should be detached so that it can be used to boot other instance. Steps to reproduce: 1. Log in to Horizon, create a new volume. 2. Create an Instance using newly created volume. 3. Verify instance is in active state. $ source devstack/openrc demo demo $ nova list +--------------------------------------+------+--------+------------+-------------+------------------+ | ID | Name | Status | Task State | Power State | Networks | +--------------------------------------+------+--------+------------+-------------+------------------+ | dae3a13b-6aa8-4794-93cd-5ab7bf90f604 | nova | ACTIVE | - | Running | private=10.0.0.3 | +--------------------------------------+------+--------+------------+-------------+------------------+ Note: Use shelve-unshelve api to see the instance goes into error state. unshelving volumed back instance does not work and sets instance state to error state (ref: https://bugs.launchpad.net/nova/+bug/1404801) 4. Shelve the instance $ nova shelve <instance-uuid> 5. Verify the status is SHELVED_OFFLOADED. $ nova list +--------------------------------------+------+-------------------+------------+-------------+------------------+ | ID | Name | Status | Task State | Power State | Networks | +--------------------------------------+------+-------------------+------------+-------------+------------------+ | dae3a13b-6aa8-4794-93cd-5ab7bf90f604 | nova | SHELVED_OFFLOADED | - | Shutdown | private=10.0.0.3 | +--------------------------------------+------+-------------------+------------+-------------+------------------+ 6. Unshelve the instance. $ nova unshelve <instance-uuid> 5. Verify the instance is in Error state. $ nova list +--------------------------------------+------+-------------------+------------+-------------+------------------+ | ID | Name | Status | Task State | Power State | Networks | +--------------------------------------+------+-------------------+------------+-------------+------------------+ | dae3a13b-6aa8-4794-93cd-5ab7bf90f604 | nova | Error | unshelving | Spawning | private=10.0.0.3 | +--------------------------------------+------+-------------------+------------+-------------+------------------+ 6. Delete the instance using Horizon. 7. Verify that volume still in in-use state $ cinder list +--------------------------------------+--------+------+------+-------------+----------+--------------------------------------+ | ID | Status | Name | Size | Volume Type | Bootable | Attached to | +--------------------------------------+--------+------+------+-------------+----------+--------------------------------------+ | 4aeefd25-10aa-42c2-9a2d-1c89a95b4d4f | in-use | test | 1 | lvmdriver-1 | true | 8f7bdc24-1891-4bbb-8f0c-732b9cbecae7 | +--------------------------------------+--------+------+------+-------------+----------+--------------------------------------+ 8. In Horizon, volume "Attached To" information is displayed as "Attached to None on /dev/vda". 9. User is not able to delete this volume, or attached it to another instance as it is still in use.
2014-12-22 12:17:55 Abhishek Kekane nova: assignee Abhishek Kekane (abhishek-kekane)
2014-12-22 17:47:15 Tushar Patil summary Volume remains in-use status, if instance booted from volume deleted when it is in the error state Volume remains in-use status, if instance booted from volume is deleted in error state
2014-12-23 01:21:57 Liyingjun nova: status New Confirmed
2015-01-05 03:37:04 Koji Iida bug added subscriber Koji Iida
2015-01-08 10:25:25 OpenStack Infra nova: status Confirmed In Progress
2015-01-08 10:25:25 OpenStack Infra nova: assignee Abhishek Kekane (abhishek-kekane) Ankit Agrawal (ankitagrawal)
2015-01-15 09:57:25 Tomoko Inoue bug added subscriber Tomoko Inoue
2015-02-18 16:34:47 Davanum Srinivas (DIMS) nova: importance Undecided Low
2015-04-20 17:54:04 melanie witt tags ntt compute
2015-05-16 05:03:52 OpenStack Infra nova: status In Progress Fix Committed
2015-06-02 06:11:09 Ankit Agrawal nova: status Fix Committed In Progress
2015-06-11 15:33:21 Matt Riedemann nova: status In Progress New
2015-06-11 18:35:08 Ankit Agrawal nova: status New In Progress
2015-06-24 13:15:28 Feodor Tersin bug added subscriber Feodor Tersin
2015-11-27 19:33:02 OpenStack Infra nova: status In Progress Fix Committed
2015-12-03 19:17:21 melanie witt nova: status Fix Committed New
2015-12-10 19:03:33 OpenStack Infra nova: status New In Progress
2015-12-10 19:03:33 OpenStack Infra nova: assignee Ankit Agrawal (ankitagrawal) Samuel Matzek (smatzek)
2016-06-29 13:38:01 OpenStack Infra nova: status In Progress Fix Released
2016-06-29 22:25:02 melanie witt nova: status Fix Released Confirmed
2016-06-29 22:51:56 OpenStack Infra nova: status Confirmed In Progress
2016-06-29 22:51:56 OpenStack Infra nova: assignee Samuel Matzek (smatzek) melanie witt (melwitt)
2016-07-07 09:27:54 OpenStack Infra nova: status In Progress Fix Released
2016-07-11 23:03:13 melanie witt nova: status Fix Released Confirmed
2016-07-11 23:40:16 OpenStack Infra nova: status Confirmed In Progress
2018-01-30 00:15:16 melanie witt nova: importance Low Medium
2018-02-13 09:28:44 OpenStack Infra nova: assignee melanie witt (melwitt) Charlotte Han (hanrong)
2018-02-15 00:09:12 OpenStack Infra nova: assignee Charlotte Han (hanrong) Mohammed Naser (mnaser)
2018-02-15 21:37:39 OpenStack Infra nova: assignee Mohammed Naser (mnaser) Matt Riedemann (mriedem)
2018-02-16 06:13:38 OpenStack Infra nova: assignee Matt Riedemann (mriedem) melanie witt (melwitt)
2018-02-20 15:34:47 OpenStack Infra nova: assignee melanie witt (melwitt) Matt Riedemann (mriedem)
2018-02-20 18:52:37 Matt Riedemann nominated for series nova/pike
2018-02-20 18:52:37 Matt Riedemann bug task added nova/pike
2018-02-20 18:52:37 Matt Riedemann nominated for series nova/queens
2018-02-20 18:52:37 Matt Riedemann bug task added nova/queens
2018-02-20 18:52:49 Matt Riedemann nova: assignee Matt Riedemann (mriedem) melanie witt (melwitt)
2018-02-20 18:52:52 Matt Riedemann nova/pike: status New In Progress
2018-02-20 18:52:54 Matt Riedemann nova/queens: status New In Progress
2018-02-20 18:52:56 Matt Riedemann nova/pike: importance Undecided Medium
2018-02-20 18:52:58 Matt Riedemann nova/queens: importance Undecided Medium
2018-02-20 18:53:05 Matt Riedemann nova/pike: assignee Mohammed Naser (mnaser)
2018-02-20 18:53:09 Matt Riedemann nova/queens: assignee Mohammed Naser (mnaser)
2018-02-21 03:17:29 OpenStack Infra nova: status In Progress Fix Released
2018-02-22 02:39:49 Matt Riedemann nominated for series nova/ocata
2018-02-22 02:39:49 Matt Riedemann bug task added nova/ocata
2018-02-22 02:39:57 Matt Riedemann nova/ocata: assignee Mohammed Naser (mnaser)
2018-02-22 02:40:00 Matt Riedemann nova/ocata: status New In Progress
2018-02-22 02:40:19 Matt Riedemann nova/ocata: importance Undecided Medium
2018-02-22 07:12:35 OpenStack Infra tags compute compute in-stable-queens
2018-02-22 08:19:23 OpenStack Infra nova/queens: status In Progress Fix Committed
2018-02-27 15:04:58 OpenStack Infra tags compute in-stable-queens compute in-stable-pike in-stable-queens
2018-03-01 14:39:50 OpenStack Infra nova/pike: status In Progress Fix Committed
2018-10-02 15:29:18 Matt Riedemann bug task deleted nova/ocata