yahoo-eng-team team mailing list archive

[Tong Liu <lexuns@xxxxxxxxx>]

Public bug reported:

For some reason, instance can be stuck in scheduling or error state,
e.g. incompatible image, lack of property in image. In this case, the
neutron port is not deleted after instance has been deleted.

This happens with recent trunk. By default, devstack creates a KVM image
without --property hypervisor_type=qemu. Instance boot with this image
is stuck in scheduling state. Port is still there after delete this
instance.

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

Title:
  Neutron port is not deleted after instance is deleted

Status in OpenStack Compute (nova):
  New

Bug description:
  For some reason, instance can be stuck in scheduling or error state,
  e.g. incompatible image, lack of property in image. In this case, the
  neutron port is not deleted after instance has been deleted.

  This happens with recent trunk. By default, devstack creates a KVM
  image without --property hypervisor_type=qemu. Instance boot with this
  image is stuck in scheduling state. Port is still there after delete
  this instance.

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