tap flows on the same source port may be duplicate due to the same tap-service and different direction

[qyq]

multiple tap-flows that have the same tap-service and different direction may exist on the same source port,which results in a conflict when deleting one of the tap-flow.
e.g
# neutron tap-flow-create --port 62cfae8e-7770-4527-91ca-b1ba7b9af0bd --tap-service c9bbb9d9-4cf1-4eaf-b2a1-1565fb42f6a2 --name src1 --direction OUT

then...

# neutron tap-flow-create --port 62cfae8e-7770-4527-91ca-b1ba7b9af0bd --tap-service c9bbb9d9-4cf1-4eaf-b2a1-1565fb42f6a2 --name src1 --direction IN

then...
# neutron tap-flow-create --port 62cfae8e-7770-4527-91ca-b1ba7b9af0bd --tap-service c9bbb9d9-4cf1-4eaf-b2a1-1565fb42f6a2 --name src1 --direction BOTH

is legal in the taas

[YAMAMOTO Takashi (yamamoto)]

it seems like a bug. what happens when removing one of them?

[qyq (qianyuqiao)]

If I delete one of them, all rules on the ovs related to the source port will be removed, but in database there still exists the tap-flow on the source port