Cisco nexus plugin fails to untrunk vlan if other hosts using vlan
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
neutron |
Fix Released
|
Low
|
Dane LeBlanc | ||
Havana |
Fix Released
|
Low
|
Dane LeBlanc |
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.
Changed in neutron: | |
assignee: | nobody → Dane LeBlanc (leblancd) |
Changed in neutron: | |
milestone: | none → icehouse-1 |
status: | Fix Committed → Fix Released |
tags: | added: havana-backport-potential |
Changed in neutron: | |
importance: | Undecided → Low |
tags: | removed: havana-backport-potential |
Changed in neutron: | |
milestone: | icehouse-1 → 2014.1 |
Fix proposed to branch: master /review. openstack. org/54612
Review: https:/