yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #03350
[Bug 1173048] Re: Quantum 2013.1 does not seem to delete the corresponding OVS port after a VM is deleted
[Expired for neutron because there has been no activity for 60 days.]
** Changed in: neutron
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1173048
Title:
Quantum 2013.1 does not seem to delete the corresponding OVS port
after a VM is deleted
Status in OpenStack Neutron (virtual network service):
Expired
Bug description:
After VMs are deleted, the OVS ports are still left behind with both
config: DOWN and state:LINK_DOWN. Should Quantum remove the ports from
OVS and the corresponding kernel physical interfaces?
# ovs-ofctl show br-int
OFPT_FEATURES_REPLY (xid=0x1): ver:0x1, dpid:0000c2eadee8b041
n_tables:255, n_buffers:256
features: capabilities:0xc7, actions:0xfff
3(int-br-eth2): addr:de:b0:3f:ca:ad:8a
config: 0
state: 0
current: 10GB-FD COPPER
4(tap7a1729aa-97): addr:e4:00:00:00:00:00 <------- for deleted VM1
config: PORT_DOWN
state: LINK_DOWN
5(tap531dad36-fa): addr:e4:00:00:00:00:00 <------- for deleted VM2
config: PORT_DOWN
state: LINK_DOWN
6(qvo596554e6-82): addr:22:f2:da:c2:d8:38
config: 0
state: 0
current: 10GB-FD COPPER
7(qvo19dfd000-40): addr:1a:ab:e2:27:13:95
config: 0
state: 0
current: 10GB-FD COPPER
8(qvo19c20971-9c): addr:86:2a:11:ec:7e:22
config: 0
state: 0
current: 10GB-FD COPPER
9(qvo36608c53-72): addr:aa:56:36:a3:b3:b4
config: 0
state: 0
current: 10GB-FD COPPER
10(qvo39bb2d60-8d): addr:46:b6:bf:45:d0:03
config: 0
state: 0
current: 10GB-FD COPPER
LOCAL(br-int): addr:c2:ea:de:e8:b0:41
config: 0
state: 0
OFPT_GET_CONFIG_REPLY (xid=0x3): frags=normal miss_send_len=0
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1173048/+subscriptions