yahoo-eng-team team mailing list archive

[Balazs Gibizer <1939856@xxxxxxxxxxxxxxxxxx>]

Why do you expect that after you delete the VM, the VM still can be
force-deleted? I think the nova delete command already deleted the VM so
there is nothing to be force-deleted.

Marking this as Invalid. Feel free to set it back to New if you
disagree.

** Changed in: nova
       Status: New => Invalid

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

Title:
  delete vm after shelve vm

Status in OpenStack Compute (nova):
  Invalid

Bug description:
  Description
  ===========
  I delete vm after I have done shelve action for vm.

  Notes: I set reclaim_instance_interval = 604800 in nova.conf

  Steps to reproduce
  ==================
  It's very important to set reclaim_instance_interval = 604800 in nova.conf

  Then do steps as followed:

      $ nova boot --flavor <flavor-id> --image <image-id> --nic net-id=<net-id> <name>
      $ nova shelve <vm-id>
      $ nova delete <vm-id>
      $ nova force-delete <vm-id>
      ERROR (CommandError): No server with a name or ID of '856407c6-2334-4470-a1fe-d57e33535b99' exists.

  Expected result
  ===============
  The vm can be force deleted correctly.

  Actual result
  =============
  The vm can not be found.

  Find the vm from the db as followed:

      mysql> use nova_cell1;
      mysql> select vm_state,uuid,deleted from instances where uuid="856407c6-2334-4470-a1fe-d57e33535b99"\G;
                 vm_state: soft-delete
                   uuid: 856407c6-2334-4470-a1fe-d57e33535b99
                  deleted: 4

  We will find that the 'deleted' field is not 0.

  Environment
  ===========
  Deploy with master of devstack.

  Logs & Configs
  ==============
  No error from log.

  nova.conf config with reclaim_instance_interval = 604800

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