yahoo-eng-team team mailing list archive

[OpenStack Infra <1831771@xxxxxxxxxxxxxxxxxx>]

This issue was fixed in the openstack/nova rocky-eol  release.

** Changed in: nova/rocky
       Status: Fix Committed => Fix Released

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

Title:
  UnexpectedDeletingTaskStateError exception can leave traces of VIFs on
  host

Status in OpenStack Compute (nova):
  Fix Released
Status in OpenStack Compute (nova) queens series:
  Fix Released
Status in OpenStack Compute (nova) rocky series:
  Fix Released
Status in OpenStack Compute (nova) stein series:
  Fix Released
Status in OpenStack Compute (nova) train series:
  Fix Released

Bug description:
  This was originally reported in Bugzilla

  https://bugzilla.redhat.com/show_bug.cgi?id=1668159

  The 'UnexpectedDeletingTaskStateError' exception can be raised by
  something like aborting a large heat stack, where the instance hasn't
  finished setting up before the stack is aborted and the instances
  deleted.

  https://github.com/openstack/nova/blob/19.0.0/nova/db/sqlalchemy/api.py#L2864

  We handle this in the compute manager and as part of that handling, we
  clean up the resource tracking of network interfaces.

  https://github.com/openstack/nova/blob/19.0.0/nova/compute/manager.py#L2034-L2040

  However, we don't unplug these interfaces. This can result in things
  being left over on the host.

  We should attempt to unplug VIFs as part of this cleanup.

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