yahoo-eng-team team mailing list archive

[Max <2088066@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

If an instance gets deleted during the building phase,
it could be that there are leftover volumes (volumes with BDM to a not
existing server in cinder).

We observed this behaviour for instances that got scheduled more than once.
This can especially happen when the instance build gets retried
by the scheduler(scheduler max_attempts > 1 setting) and the instance
gets deleted after the first failed build/build on first host.

This results in an BDM entry on cinder side to an non existing server 
and the boot volume will stay in reserved.


A quick fix could be to check for ports and volumes during the delete api call in the may_have_ports_or_volumes function.

** 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/2088066

Title:
  leftover BDM during deletion of building instances

Status in OpenStack Compute (nova):
  New

Bug description:
  If an instance gets deleted during the building phase,
  it could be that there are leftover volumes (volumes with BDM to a not
  existing server in cinder).

  We observed this behaviour for instances that got scheduled more than once.
  This can especially happen when the instance build gets retried
  by the scheduler(scheduler max_attempts > 1 setting) and the instance
  gets deleted after the first failed build/build on first host.

  This results in an BDM entry on cinder side to an non existing server 
  and the boot volume will stay in reserved.

  
  A quick fix could be to check for ports and volumes during the delete api call in the may_have_ports_or_volumes function.

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