yahoo-eng-team team mailing list archive

[Drew Thorstensen <thorst@xxxxxxxxxx>]

Public bug reported:

When the interface-attach action is run, it may be passed in a network
(but no port identifier).  Therefore, the action allocates a port on
that network.  However, if the attach method fails for some reason, the
port is not cleaned up.

This behavior would be appropriate if the invoker had passed in a port
identifier.  However if nova created the port for the action and that
action failed, the port should be cleaned up as part of the failure.

The allocation of the port occurs in nova/compute/manager.py in the
attach_interface method.  Recommend that we de-allocate the port for the
instance had no port_id been passed in.

** Affects: nova
     Importance: Undecided
     Assignee: Drew Thorstensen (thorst)
         Status: New

** Changed in: nova
     Assignee: (unassigned) => Drew Thorstensen (thorst)

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

Title:
  Failure in interface-attach may leave port around

Status in OpenStack Compute (Nova):
  New

Bug description:
  When the interface-attach action is run, it may be passed in a network
  (but no port identifier).  Therefore, the action allocates a port on
  that network.  However, if the attach method fails for some reason,
  the port is not cleaned up.

  This behavior would be appropriate if the invoker had passed in a port
  identifier.  However if nova created the port for the action and that
  action failed, the port should be cleaned up as part of the failure.

  The allocation of the port occurs in nova/compute/manager.py in the
  attach_interface method.  Recommend that we de-allocate the port for
  the instance had no port_id been passed in.

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