tap-service and tap-flow are always DOWN
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tap-as-a-service |
In Progress
|
Undecided
|
Lajos Katona |
Bug Description
I am trying to mirror traffic in the simplest scenario ever.
I have deployed a devstack and have the following configuration:
```
cat ~/Git/devstack/
[[local|localrc]]
ADMIN_PASSWORD=
DATABASE_
RABBIT_
SERVICE_
#IPV4_ADDRS_
#FLOATING_
#HOST_IP=10.3.4.5
enable_plugin tap-as-a-service https:/
enable_service taas
TAAS_SERVICE_
```
After everything is up. I create src_port (security port ENABLED) and target_port (security port DISABLED). I create VM1 and attach src_port and VM2 and attach target_port.
The VMS are up and can reach one another.
Then I run the following commands:
```
openstack tap service create --name TS --port target_port
+------
| Field | Value |
+------
| description | |
| id | 1c6f212f-
| name | TS |
| port_id | 872c46e0-
| project_id | 3ca99d765f8d4fe
| status | DOWN |
+------
openstack tap flow create --name TF --port src_port --tap-service TS --direction BOTH
+------
| Field | Value |
+------
| description | |
| direction | BOTH |
| id | 43955fad-
| name | TF |
| project_id | 3ca99d765f8d4fe
| source_port | 4d9e899d-
| status | DOWN |
| tap_service_id | 1c6f212f-
| vlan_filter | None |
+------
```
Notice that in both service and flow status is DOWN and the traffic is not mirrored in VM2.
Checked all logs with journalctl devstack@*, but no error found, any ideas?
Changed in tap-as-a-service: | |
status: | Incomplete → Confirmed |
Changed in tap-as-a-service: | |
status: | Confirmed → In Progress |
Hi, thanks for the bug report.
I just quickly run through your local.conf snippet and saw some suspicious things:
* enable_plugin tap-as-a-service https:/ /opendev. org/x/tap- as-a-service /github/ tap-as- a-service master
** tap-as-a-service was moved under openstack namespace, so the correct line:
** enable_plugin tap-as-a-service file://
* For Neutron and devstack the default networking backend is OVN,but for taas you need OVS: SERVICES+ =,q-svc, q-agt,q- dhcp,q- meta,q- l3,q-trunk, q-segment, taas, MECHANISM_ DRIVERS= openvswitch
ENABLED_
(or with enable_service list the above services please)
To use OVS as mech driver I think you need these lines also:
Q_PLUGIN=ml2
Q_AGENT=openvswitch
Q_ML2_PLUGIN_
To be on the safe side after devstack is ready, check Neutron cfg files under /etc/neutron folder: plugins/ ml2/ml2_ conf.ini
$ grep mechanism_drivers /etc/neutron/
mechanism_drivers = openvswitch
If something still doesn't work please come back here or ask on Neutron IRC channel (on irc.oftc.net, #openstack-neutron channel)