← Back to team overview

yahoo-eng-team team mailing list archive

[Bug 1378683] [NEW] nova-cell, cannot delete VM once deleting VM with failure in nova-compute

 

Public bug reported:

Not able to delete the VM once the VM deletion failed in nova compute.

Steps to reproduce:

1. create VM
2. wait until VM becomes available
3. Stop nova-cell child process
4. delete VM
   nova delete <vm_id or vm_name>
5. stop neutron service
6. start child nova-cell process
7. start neutron service
8. delete VM again

VM is not deleted and will be listed in the nova list output.

$ nova list
+--------------------------------------+------+--------+------------+-------------+------------------+
| ID                                   | Name | Status | Task State | Power State | Networks         |
+--------------------------------------+------+--------+------------+-------------+------------------+
| 9d7c9fb2-010f-4de6-975a-1a2de825155b | vm09 | ERROR  | -          | Running     | private=10.0.0.2 |
+--------------------------------------+------+--------+------------+-------------+------------------+

Following log messages is logged in n-child-cell screen:

2014-10-07 04:36:57.159 INFO nova.compute.api [req-11c20157-23ac-4892-9fdf-3e60201a9bb4 admin admin]
[instance: 77aabf6c-7b33-4c49-8061-eb9805214085] Instance is already in deleting state, ignoring this request

Note: VM never gets deleted.

** Affects: nova
     Importance: Undecided
     Assignee: Rajesh Tailor (rajesh-tailor)
         Status: New


** Tags: ntt

** Changed in: nova
     Assignee: (unassigned) => Rajesh Tailor (rajesh-tailor)

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

Title:
  nova-cell, cannot delete VM once deleting VM with failure in nova-
  compute

Status in OpenStack Compute (Nova):
  New

Bug description:
  Not able to delete the VM once the VM deletion failed in nova compute.

  Steps to reproduce:

  1. create VM
  2. wait until VM becomes available
  3. Stop nova-cell child process
  4. delete VM
     nova delete <vm_id or vm_name>
  5. stop neutron service
  6. start child nova-cell process
  7. start neutron service
  8. delete VM again

  VM is not deleted and will be listed in the nova list output.

  $ nova list
  +--------------------------------------+------+--------+------------+-------------+------------------+
  | ID                                   | Name | Status | Task State | Power State | Networks         |
  +--------------------------------------+------+--------+------------+-------------+------------------+
  | 9d7c9fb2-010f-4de6-975a-1a2de825155b | vm09 | ERROR  | -          | Running     | private=10.0.0.2 |
  +--------------------------------------+------+--------+------------+-------------+------------------+

  Following log messages is logged in n-child-cell screen:

  2014-10-07 04:36:57.159 INFO nova.compute.api [req-11c20157-23ac-4892-9fdf-3e60201a9bb4 admin admin]
  [instance: 77aabf6c-7b33-4c49-8061-eb9805214085] Instance is already in deleting state, ignoring this request

  Note: VM never gets deleted.

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


Follow ups

References