+++ This bug was initially created as a clone of Bug #1982743 +++ Description of problem: When restarting ovs, if it contains a flow that matches igmp traffic, ovs-ctl fails to restore the flows (and in fact all flows on the bridge are lost). Version-Release number of selected component (if applicable): Tested with latest (and upstream) openvswitch2.15 How reproducible: Always Steps to Reproduce: 1. /usr/share/openvswitch/scripts/ovs-ctl start openvswitch 2. ovs-vsctl add-br br0 3. ovs-ofctl add-flow br0 "ip,nw_proto=2 actions=drop" 4. /usr/share/openvswitch/scripts/ovs-ctl restart openvswitch Actual results: /usr/share/openvswitch/scripts/ovs-ctl restart Saving flows [ OK ] Exiting ovsdb-server (2041630) [ OK ] Starting ovsdb-server [ OK ] system ID not configured, please use --system-id ... failed! Configuring Open vSwitch system IDs [ OK ] Exiting ovs-vswitchd (2041671) [ OK ] Starting ovs-vswitchd [ OK ] Restoring saved flows ovs-ofctl: /tmp/ovs-save.FmwE0BbwhG/br0.flows.dump:2: field igmp missing value $ ovs-ofctl dump-flows br0 (Does not contain flows after offending flow) Expected results: Error should not be generated and flows should be restored Additional info: --- Additional comment from Red Hat Bugzilla on 2021-09-21 10:02:10 UTC --- remove performed by PnT Account Manager <pnt-expunge>
Please confirm that this BZ is for the fix in openvswitch2.13-2.13.0-113.el7fdp. I'm asking because comment #1 indicates it for errata https://errata.devel.redhat.com/advisory/89442 which is for package openvswitch2.13-2.13.0-162.el8fdp.
For clarification, the question is: is this BZ for the fix in OVS for el7 or in el8 because there is no errata for el7.
I am marking this as Verified (see notes below). I confirmed that this fix is for el7 as the BZ that added the fix to OVS 2.13 for RHEL-8 is [1] which was part of FDP 22.A OVS 2.13 RHEL-8 errata [2]. I believe this BZ should be removed from FDP 22.B OVS 2.13 RHEL-8 errata [3]. [1] https://bugzilla.redhat.com/show_bug.cgi?id=2029944 [2] https://errata.devel.redhat.com/advisory/86957 [3] https://errata.devel.redhat.com/advisory/89442 Reproduced isue using openvswitch2.13-2.13.0-112.el7fdp.x86_64: [root@netqe9 ~]# uname -r 3.10.0-1160.59.1.el7.x86_64 [root@netqe9 ~]# rpm -qa | grep openvswitch openvswitch-selinux-extra-policy-1.0-18.el7fdp.noarch openvswitch2.13-2.13.0-112.el7fdp.x86_64 [root@netqe9 ~]# /usr/share/openvswitch/scripts/ovs-ctl start ovsdb-server is already running. ovs-vswitchd is already running. Enabling remote OVSDB managers [ OK ] [root@netqe9 ~]# ovs-vsctl --if-exists del-br br0 [root@netqe9 ~]# ovs-vsctl add-br br0 [root@netqe9 ~]# ovs-ofctl del-flows br0 [root@netqe9 ~]# ovs-ofctl add-flow br0 "ip,nw_proto=2 actions=drop" [root@netqe9 ~]# ovs-ofctl add-flow br0 in_port=1,idle_timeout=0,actions=output:1 [root@netqe9 ~]# ovs-ofctl add-flow br0 in_port=2,idle_timeout=0,actions=output:2 [root@netqe9 ~]# ovs-ofctl dump-flows br0 cookie=0x0, duration=11.780s, table=0, n_packets=0, n_bytes=0, igmp actions=drop cookie=0x0, duration=11.770s, table=0, n_packets=0, n_bytes=0, in_port=1 actions=output:1 cookie=0x0, duration=11.759s, table=0, n_packets=0, n_bytes=0, in_port=2 actions=output:2 [root@netqe9 ~]# /usr/share/openvswitch/scripts/ovs-ctl restart Saving flows [ OK ] Exiting ovsdb-server (17461) [ OK ] Starting ovsdb-server [ OK ] system ID not configured, please use --system-id ... failed! Configuring Open vSwitch system IDs [ OK ] Exiting ovs-vswitchd (17536) [ OK ] Starting ovs-vswitchd [ OK ] Restoring saved flows ovs-ofctl: /tmp/ovs-save.xGfNpsZi3s/br0.flows.dump:1: field igmp missing value [ OK ] Enabling remote OVSDB managers [ OK ] [root@netqe9 ~]# ovs-ofctl dump-flows br0 cookie=0x0, duration=3.146s, table=0, n_packets=0, n_bytes=0, priority=0 actions=NORMAL [root@netqe9 ~]# Verified fix in openvswitch2.13-2.13.0-132.el7fdp.x86_644: [root@netqe9 ~]# uname -r 3.10.0-1160.59.1.el7.x86_64 [root@netqe9 ~]# rpm -qa | grep openvswitch openvswitch-selinux-extra-policy-1.0-18.el7fdp.noarch openvswitch2.13-2.13.0-132.el7fdp.x86_64 [root@netqe9 ~]# /usr/share/openvswitch/scripts/ovs-ctl start /etc/openvswitch/conf.db does not exist ... (warning). Creating empty database /etc/openvswitch/conf.db [ OK ] Starting ovsdb-server [ OK ] system ID not configured, please use --system-id ... failed! Configuring Open vSwitch system IDs [ OK ] Inserting openvswitch module [ OK ] Starting ovs-vswitchd [ OK ] Enabling remote OVSDB managers [ OK ] [root@netqe9 ~]# ovs-vsctl --if-exists del-br br0 [root@netqe9 ~]# ovs-vsctl add-br br0 [root@netqe9 ~]# ovs-ofctl del-flows br0 [root@netqe9 ~]# ovs-ofctl add-flow br0 "ip,nw_proto=2 actions=drop" [root@netqe9 ~]# ovs-ofctl add-flow br0 in_port=1,idle_timeout=0,actions=output:1 [root@netqe9 ~]# ovs-ofctl add-flow br0 in_port=2,idle_timeout=0,actions=output:2 [root@netqe9 ~]# ovs-ofctl dump-flows br0 cookie=0x0, duration=12.030s, table=0, n_packets=0, n_bytes=0, igmp actions=drop cookie=0x0, duration=12.020s, table=0, n_packets=0, n_bytes=0, in_port=1 actions=output:1 cookie=0x0, duration=12.009s, table=0, n_packets=0, n_bytes=0, in_port=2 actions=output:2 [root@netqe9 ~]# /usr/share/openvswitch/scripts/ovs-ctl restart Saving flows [ OK ] Exiting ovsdb-server (17299) [ OK ] Starting ovsdb-server [ OK ] system ID not configured, please use --system-id ... failed! Configuring Open vSwitch system IDs [ OK ] Exiting ovs-vswitchd (17326) [ OK ] Starting ovs-vswitchd [ OK ] Restoring saved flows [ OK ] Enabling remote OVSDB managers [ OK ] [root@netqe9 ~]# ovs-ofctl dump-flows br0 cookie=0x0, duration=10.646s, table=0, n_packets=0, n_bytes=0, igmp actions=drop cookie=0x0, duration=10.646s, table=0, n_packets=0, n_bytes=0, in_port=1 actions=output:1 cookie=0x0, duration=10.646s, table=0, n_packets=0, n_bytes=0, in_port=2 actions=output:2 [root@netqe9 ~]#
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (openvswitch2.13 bug fix and enhancement update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2022:1147