yahoo-eng-team team mailing list archive

[Carol Bouchard <caboucha@xxxxxxxxx>]

After testing, I found this is not a bug.  This is related to 1330597 which deals with add of vlan while one already exists.
This bug is intended to address removal of vlan while the user's vlan must stay intact.  Here are the tests.

If you add your instance which creates your vlan (109), then remove your instance, you are left with 
'switchport trunk allowed vlan none' which is the expected behavior.

If you add your instance which creates your vlan (109), then add another vlan (1) to your interface. You will see
'switchport trunk allowed vlan 1,190'.  When you remove your instance (vlan109), you are left with 
'switchport trunk allowed vlan 1'.

This bug will be marked as invalid due to these results.


** Changed in: neutron
       Status: New => Invalid

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

Title:
  ML2 Cisco Nexus MD: Don't delete a VLAN with existing Configuration

Status in OpenStack Neutron (virtual network service):
  Invalid

Bug description:
  If an existing configuration is already present on a switchport VLAN
  interface before Openstack adds the VLAN, then, at the time of
  deleting the Openstack VLAN, do not delete the config already present.

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