ovs flows are not readded when ovsdb-server/ovs-vswitchd are restarted.

Bug #1912651 reported by Marc Gariépy
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
neutron
Fix Committed
Medium
Marc Gariépy

Bug Description

when there ovsdb-server and ovs-vswitchd are restarted, neutron-openvswitch-agent doesn't add the conjunction flows back.

http://paste.openstack.org/show/801819/

when restarting the neutron-openvswitch-agent all the flows are re-added correctly.

plugins/ml2/openvswitch_agent.ini:firewall_driver = openvswitch

i'm currently using Openstack Ussuri

== reproduce with ==
1. spawn a couple vms in your cloud
2. dump the flow : ovs-ofctl dump-flows br-int
3. restart ovsdb-server and ovs-switchd (this happens when pkg are updated also)
4- dump the flow and compare what's missing.

Tags: ovs
Marc Gariépy (mgariepy)
description: updated
Revision history for this message
LIU Yulong (dragon889) wrote :

Confirmed, I could reproduce this bug. After restart the openvswitch (ovs-db and vswitchd), these types of flows lost:
table=82, priority=70,ct_state=+est-rel-rpl,ipv6,reg6=0x3,ipv6_src=[*] actions=conjunction(*,1/2)
table=82, priority=70,ct_state=+new-est,ipv6,reg6=0x3,ipv6_src=[*] actions=conjunction(*,1/2)

table=82, priority=70,ct_state=+est-rel-rpl,ip,reg6=0x3,nw_src=[*] actions=conjunction(*,1/2)
table=82, priority=70,ct_state=+new-est,ip,reg6=0x3,nw_src=[*] actions=conjunction(17,1/2)

Changed in neutron:
status: New → Confirmed
importance: Undecided → Medium
tags: added: ovs
Revision history for this message
Marc Gariépy (mgariepy) wrote :
Changed in neutron:
assignee: nobody → Marc Gariépy (mgariepy)
Marc Gariépy (mgariepy)
Changed in neutron:
status: Confirmed → Fix Committed
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/neutron 15.3.3

This issue was fixed in the openstack/neutron 15.3.3 release.

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/neutron 16.3.1

This issue was fixed in the openstack/neutron 16.3.1 release.

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/neutron 17.1.1

This issue was fixed in the openstack/neutron 17.1.1 release.

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/neutron 18.0.0.0rc1

This issue was fixed in the openstack/neutron 18.0.0.0rc1 release candidate.

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/neutron queens-eol

This issue was fixed in the openstack/neutron queens-eol release.

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/neutron rocky-eol

This issue was fixed in the openstack/neutron rocky-eol release.

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/neutron stein-eol

This issue was fixed in the openstack/neutron stein-eol release.

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.