br-tap flow rules configured by tap-service disappear after ovs restarts

[qyq]

First, execute cmd:

neutron tap-service-create --name dst1 --port 7db38629-39b7-46f7-935c-46e74cdb2dbf

After I restart the ovs,the openflow rules added after I execute above command previouesly on br-tap will disappear,so are the openflow rules configured by tap-service on br-int

[YAMAMOTO Takashi (yamamoto)]

can you elaborate a bit more?
it's normal for openflow rules disappearing on a restart.

[qyq (qianyuqiao)]

Thank you for your prompt reply,The problem is as follows:
1.create a tap-service on a desination port
2.create a tap-flow on the mirrored on port
3.After the actions above,I can see br-tap, br-int,and br-tun have added some extra openflow rules related to mirrored port traffic forwarding.
for example,if I create a tap-service on host1, the br-int on host1 should add openflow rules as follows:

table=0,priority=25,in_port=patch-int-tap,dl_vlan=3900,actions=mod_vlan_vid:port_vlan_id,output:ovs_port_id

4.restart the ovs service and restart the neutron-openvswitch-agent,the above rules disappear.more accurately,the flows added after I execute step1 and step2 will all disappear.So the tap-service and tap-flow did not work.I wonder whether it is a bug?the tap-service and tap-flow should have worked after the neutron-openvswitch-agent restarts.
Also, I have read the codes of tap-as-a-service,and I did not see any codes copying with such situation

[Bence Romsics (bence-romsics)]

I also ran into this problem and I'd like to add some details. Tested the effect of ovs restarts on a host with only a tap flow and on another with only a tap service.

ml2/ovs users are used to that ovs-agent detects when ovs was restarted and reinstalls its flows after. However this does not happen for taas flows.

After an ovs restart and flows being lost, a tap service can be recovered just by restarting ovs-agent.

After an ovs restart and flows being lost, a tap flow cannot be recovered just by restarting ovs-agent. After the ovs-agent restart we also need to delete and re-create the tap flow.

[xymiao (xymiao)]

hello ，I also ran into this problem and I'd like to add some details. Tested the effect of ovs restarts on a host with only a tap flow and on another with only a tap service.

ml2/ovs users are used to that ovs-agent detects when ovs was restarted and reinstalls its flows after. However this does not happen for taas flows.

After an ovs restart and flows being lost, a tap service can be recovered just by restarting ovs-agent.

After an ovs restart and flows being lost, a tap flow cannot be recovered just by restarting ovs-agent. After the ovs-agent restart we also need to delete and re-create the tap flow.