Trunk bridges aren't removed
Bug #1914886 reported by
Slawek Kaplonski
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
neutron |
Invalid
|
Undecided
|
Rodolfo Alonso | ||
os-vif |
Invalid
|
Medium
|
sean mooney |
Bug Description
Recently I found out on the devstack that when I have VM with trunk port and some subports connected to it, trunk bridge isn't deleted when VM is migrated to the another host.
I think that the same thing will happen when instance will be simply deleted as vif object in case of trunk port (when ML2/ovs is used on Neutron's side) is objects.
Changed in os-vif: | |
assignee: | nobody → sean mooney (sean-k-mooney) |
status: | New → Triaged |
importance: | Undecided → Medium |
Changed in neutron: | |
assignee: | nobody → Rodolfo Alonso (rodolfo-alonso-hernandez) |
tags: | added: trunk |
Changed in neutron: | |
status: | New → Incomplete |
To post a comment you must log in.
Hello:
As commented in IRC, Nova needs to know if a port belongs to a trunk (actually if this port is the trunk parent port). Neutron provides this info in the port GET result. From the result dictionary in the HTTP request: http:// paste.openstack .org/show/ 807221/
"port.trunk_ details" contains the trunk ID and the subports info.
Sean, do you need something else?
Regards.