taas can create tap-flow on the source port down without any error info but new rules not added even the port is up later
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tap-as-a-service |
Confirmed
|
High
|
Unassigned |
Bug Description
Openstack version: Queens
Let's Reproduce the bug:
1.create a tap-flow on a neutron port down, we can get the success result on the console
# neutron tap-flow-create --name src1 --tenant-id 94b35ccc0916477
neutron CLI is deprecated and will be removed in the future. Use openstack CLI instead.
Created a new tap_flow:
+------
| Field | Value |
+------
| description | |
| direction | BOTH |
| id | 2e861b97-
| name | src1 |
| project_id | 94b35ccc0916477
| source_port | 62cfae8e-
| status | ACTIVE |
| tap_service_id | c1cf4617-
| tenant_id | 94b35ccc0916477
+------
note the flow source port is down now
# openstack port list | grep 62cfae8e-
| 62cfae8e-
2.start the Vm binding the port, now the port is up
| 62cfae8e-
3.After a while, Let's check the br-int openflow rules on which there is the source port,I do not see the rules which shoud be added by tap-flow-create on br-int,you can verify it by execute:
# ovs-ofctl dump-flows br-int | grep mod_vlan_vid
and the result is empty.
"taas can create tap-flow on the source port down without any error info" is an expected behavior.
"new rules not added even the port is up later" is a bug.