ML2 Cisco Nexus MD: Don't delete a VLAN with existing Configuration
Bug #1346969 reported by
Abishek Subramanian
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| neutron |
Invalid
|
Low
|
Carol Bouchard | ||
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.
| Changed in neutron: | |
| assignee: | nobody → Abishek Subramanian (absubram) |
| tags: | added: cisco |
| Changed in neutron: | |
| importance: | Undecided → Low |
| Changed in neutron: | |
| assignee: | Abishek Subramanian (absubram) → Carol Bouchard (caboucha) |
Revision history for this message
| Carol Bouchard (caboucha) wrote | #1 |
| Changed in neutron: | |
| status: | New → Invalid |
To post a comment you must log in.
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.