yahoo-eng-team team mailing list archive

[Alan Pevec <1246080@xxxxxxxxxxxxxxxxxx>]

** Also affects: neutron/havana
   Importance: Undecided
       Status: New

** Changed in: neutron
   Importance: Undecided => Low

** Changed in: neutron/havana
   Importance: Undecided => Low

** Changed in: neutron/havana
       Status: New => In Progress

** Changed in: neutron/havana
     Assignee: (unassigned) => Dane LeBlanc (leblancd)

** Tags removed: havana-backport-potential

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1246080

Title:
  Cisco nexus plugin fails to untrunk vlan if other hosts using vlan

Status in OpenStack Neutron (virtual network service):
  Fix Released
Status in neutron havana series:
  In Progress

Bug description:
  If two or more compute hosts have instances which are
  sharing a given VLAN on a Nexus switch, and then
  all instances on one of the hosts which are using that
  VLAN are terminated, while instances which are using
  that VLAN on other hosts remain active, then
  the VLAN is not being untrunked from the
  corresponding interface on the Nexus switch as
  expected.

  Note that the VLAN is correctly untrunked from
  the Nexus interface when the instance being
  terminated is the last instance which is using that
  VLAN on the Nexus switch.

  The correct logic should be:
  If this the last instance using this VLAN on this switch interface:
  ____untrunk the vlan from the switch interface
  ____If this the last instance using this VLAN on this switch:
  _________delete the VLAN from the switch

  Note that this bug also exists in the Cisco ML2
  mechanism driver, but the code which implements
  this is being redesigned, so it will be addressed for
  the ML2 separately.

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