ovsfw + trunk scenario is broken

Bug #1672547 reported by Kevin Benton
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
neutron
Confirmed
High
Unassigned

Bug Description

Since we have switched to using the OVS firewall for the OVS scenario, the job has been failing with a timeout in connectivity.

There are errors in the agent log that look suspect:

2017-03-10 06:12:47.785 1325 ERROR neutron.agent.linux.openvswitch_firewall.firewall [req-f238f807-e8fa-42f9-bdda-0f6e374539cc - -] Initializing port 550bf67f-2007-4dfb-bb0c-b53e08f58918 that was already initialized.
2017-03-10 06:18:09.367 1325 ERROR neutron.agent.linux.openvswitch_firewall.firewall [req-8fea5fd1-d731-43f9-8c1c-a3aa87fe2223 - -] Initializing port 76ae4940-bb43-4fad-8c24-66ec2f6ffa56 that was already initialized.

Source: http://logs.openstack.org/58/442758/1/check/gate-tempest-dsvm-neutron-dvr-multinode-scenario-ubuntu-xenial-nv/9d6a1bb/logs/screen-q-agt.txt.gz?level=TRACE

Tags: ovs-fw trunk
tags: added: trunk
Revision history for this message
Armando Migliaccio (armando-migliaccio) wrote :

Closed in favor of bugs on specific failure modes.

Revision history for this message
Armando Migliaccio (armando-migliaccio) wrote :
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.