yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #68168
[Bug 1720091] [NEW] delete running vms, but ovs flow table is still residual
Public bug reported:
in Pike version, if I delete running vms, the ovs flow table will be
still residual.
for examples:
the first, create vm, named pc1
[root@bogon ~]# nova list
+--------------------------------------+------+--------+------------+-------------+--------------+
| ID | Name | Status | Task State | Power State | Networks |
+--------------------------------------+------+--------+------------+-------------+--------------+
| 2f91523c-6a4f-434a-a228-0d07ca735e6a | pc1 | ACTIVE | - | Running | net=5.5.5.13 |
+--------------------------------------+------+--------+------------+-------------+--------------+
the second,I directly delete the running virtual machine,
[root@bogon ~]# nova list
+----+------+--------+------------+-------------+----------+
| ID | Name | Status | Task State | Power State | Networks |
+----+------+--------+------------+-------------+----------+
+----+------+--------+------------+-------------+----------+
then the relevant flow table will be left.
[root@bogon ~]# ovs-ofctl dump-flows br-int | grep 5.5.5.13
cookie=0x8231b3d9ff6eecde, duration=189.590s, table=82, n_packets=0, n_bytes=0, idle_age=189, priority=70,ct_state=+est-rel-rpl,ip,reg6=0x1,nw_src=5.5.5.13 actions=conjunction(2,1/2)
cookie=0x8231b3d9ff6eecde, duration=189.589s, table=82, n_packets=0, n_bytes=0, idle_age=189, priority=70,ct_state=+new-est,ip,reg6=0x1,nw_src=5.5.5.13 actions=conjunction(3,1/2)
** Affects: neutron
Importance: Undecided
Status: New
** Tags: neutron
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1720091
Title:
delete running vms, but ovs flow table is still residual
Status in neutron:
New
Bug description:
in Pike version, if I delete running vms, the ovs flow table will be
still residual.
for examples:
the first, create vm, named pc1
[root@bogon ~]# nova list
+--------------------------------------+------+--------+------------+-------------+--------------+
| ID | Name | Status | Task State | Power State | Networks |
+--------------------------------------+------+--------+------------+-------------+--------------+
| 2f91523c-6a4f-434a-a228-0d07ca735e6a | pc1 | ACTIVE | - | Running | net=5.5.5.13 |
+--------------------------------------+------+--------+------------+-------------+--------------+
the second,I directly delete the running virtual machine,
[root@bogon ~]# nova list
+----+------+--------+------------+-------------+----------+
| ID | Name | Status | Task State | Power State | Networks |
+----+------+--------+------------+-------------+----------+
+----+------+--------+------------+-------------+----------+
then the relevant flow table will be left.
[root@bogon ~]# ovs-ofctl dump-flows br-int | grep 5.5.5.13
cookie=0x8231b3d9ff6eecde, duration=189.590s, table=82, n_packets=0, n_bytes=0, idle_age=189, priority=70,ct_state=+est-rel-rpl,ip,reg6=0x1,nw_src=5.5.5.13 actions=conjunction(2,1/2)
cookie=0x8231b3d9ff6eecde, duration=189.589s, table=82, n_packets=0, n_bytes=0, idle_age=189, priority=70,ct_state=+new-est,ip,reg6=0x1,nw_src=5.5.5.13 actions=conjunction(3,1/2)
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1720091/+subscriptions
Follow ups