yahoo-eng-team team mailing list archive

[Eric Xie <1838385@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

Description
===========
I created one instance boot from volume.
After deleting the instance when it's building,
the volume's status was reserved.

Steps to reproduce
==================
* I created one instance with `openstack server create --volume vol-for-vm1-50G --flavor ecs_2C4G50G_general --network xtt-net-1 vm1`
* then I deleted the instance when it's status was build
| 3aa10ae1-2f3f-4c52-8f27-a557cf82de9e | vm1        | BUILD  | None       | NOSTATE     |                                                     |                             |                                      | ecs_2C4G50G_general   | 5af94a8a-aab9-4ba5-bf52-ddb815218e61 | cn-north-3a       | None   |            |
* then I showed the status of volume


Expected result
===============
The volume's status is available.

Actual result
=============
The volume's status is reserved.

Environment
===========
1. Exact version of OpenStack you are running. See the following
  list for all releases: http://docs.openstack.org/releases/
  # apt list --installed | grep nova

WARNING: apt does not have a stable CLI interface. Use with caution in
scripts.

nova-api/xenial,xenial,now 2:17.0.7-6~u16.01 all [installed]
nova-common/xenial,xenial,now 2:17.0.7-6~u16.01 all [installed]
nova-conductor/xenial,xenial,now 2:17.0.7-6~u16.01 all [installed]
nova-consoleauth/xenial,xenial,now 2:17.0.7-6~u16.01 all [installed]
nova-consoleproxy/xenial,xenial,now 2:17.0.7-6~u16.01 all [installed]
nova-doc/xenial,xenial,now 2:17.0.7-6~u16.01 all [installed]
nova-placement-api/xenial,xenial,now 2:17.0.7-6~u16.01 all [installed]
nova-scheduler/xenial,xenial,now 2:17.0.7-6~u16.01 all [installed]
python-nova/xenial,xenial,now 2:17.0.7-6~u16.01 all [installed,automatic]
python-novaclient/xenial,xenial,now 2:9.1.1-1~u16.04+mcp6 all [installed,automatic]

# apt list --installed | grep cinder

WARNING: apt does not have a stable CLI interface. Use with caution in
scripts.

cinder-backup/xenial,xenial,now 2:12.0.4-2~u16.04 all [installed]
cinder-common/xenial,xenial,now 2:12.0.4-2~u16.04 all [installed,automatic]
cinder-scheduler/xenial,xenial,now 2:12.0.4-2~u16.04 all [installed]
cinder-volume/xenial,xenial,now 2:12.0.4-2~u16.04 all [installed]
python-cinder/xenial,xenial,now 2:12.0.4-2~u16.04 all [installed,automatic]
python-cinderclient/xenial,xenial,now 1:3.5.0-1.0~u16.04+mcp5 all [installed,automatic]

** Affects: nova
     Importance: Undecided
         Status: New

-- 
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/1838385

Title:
  Volume reserved after instance deleted

Status in OpenStack Compute (nova):
  New

Bug description:
  Description
  ===========
  I created one instance boot from volume.
  After deleting the instance when it's building,
  the volume's status was reserved.

  Steps to reproduce
  ==================
  * I created one instance with `openstack server create --volume vol-for-vm1-50G --flavor ecs_2C4G50G_general --network xtt-net-1 vm1`
  * then I deleted the instance when it's status was build
  | 3aa10ae1-2f3f-4c52-8f27-a557cf82de9e | vm1        | BUILD  | None       | NOSTATE     |                                                     |                             |                                      | ecs_2C4G50G_general   | 5af94a8a-aab9-4ba5-bf52-ddb815218e61 | cn-north-3a       | None   |            |
  * then I showed the status of volume

  
  Expected result
  ===============
  The volume's status is available.

  Actual result
  =============
  The volume's status is reserved.

  Environment
  ===========
  1. Exact version of OpenStack you are running. See the following
    list for all releases: http://docs.openstack.org/releases/
    # apt list --installed | grep nova

  WARNING: apt does not have a stable CLI interface. Use with caution in
  scripts.

  nova-api/xenial,xenial,now 2:17.0.7-6~u16.01 all [installed]
  nova-common/xenial,xenial,now 2:17.0.7-6~u16.01 all [installed]
  nova-conductor/xenial,xenial,now 2:17.0.7-6~u16.01 all [installed]
  nova-consoleauth/xenial,xenial,now 2:17.0.7-6~u16.01 all [installed]
  nova-consoleproxy/xenial,xenial,now 2:17.0.7-6~u16.01 all [installed]
  nova-doc/xenial,xenial,now 2:17.0.7-6~u16.01 all [installed]
  nova-placement-api/xenial,xenial,now 2:17.0.7-6~u16.01 all [installed]
  nova-scheduler/xenial,xenial,now 2:17.0.7-6~u16.01 all [installed]
  python-nova/xenial,xenial,now 2:17.0.7-6~u16.01 all [installed,automatic]
  python-novaclient/xenial,xenial,now 2:9.1.1-1~u16.04+mcp6 all [installed,automatic]

  # apt list --installed | grep cinder

  WARNING: apt does not have a stable CLI interface. Use with caution in
  scripts.

  cinder-backup/xenial,xenial,now 2:12.0.4-2~u16.04 all [installed]
  cinder-common/xenial,xenial,now 2:12.0.4-2~u16.04 all [installed,automatic]
  cinder-scheduler/xenial,xenial,now 2:12.0.4-2~u16.04 all [installed]
  cinder-volume/xenial,xenial,now 2:12.0.4-2~u16.04 all [installed]
  python-cinder/xenial,xenial,now 2:12.0.4-2~u16.04 all [installed,automatic]
  python-cinderclient/xenial,xenial,now 1:3.5.0-1.0~u16.04+mcp5 all [installed,automatic]

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1838385/+subscriptions