1759337 – [EL-8] OvS DoS'es the system on port creation failure

The FDP team is no longer accepting new bugs in Bugzilla. Please report your issues under FDP project in Jira. Thanks.

Bug 1759337 - [EL-8] OvS DoS'es the system on port creation failure

Summary: [EL-8] OvS DoS'es the system on port creation failure

Keywords:
Status:	CLOSED ERRATA
Alias:	None
Product:	Red Hat Enterprise Linux Fast Datapath
Classification:	Red Hat
Component:	openvswitch2.11
Sub Component:
Version:	RHEL 7.7
Hardware:	Unspecified
OS:	Unspecified
Priority:	low
Severity:	medium
Target Milestone:	---
Target Release:	---
Assignee:	Aaron Conole
QA Contact:	Jean-Tsung Hsiao
Docs Contact:
URL:
Whiteboard:
Depends On:	1737146
Blocks:
TreeView+	depends on / blocked

Reported:	2019-10-07 20:58 UTC by Flavio Leitner
Modified:	2021-03-09 08:20 UTC (History)
CC List:	10 users (show)
Fixed In Version:	openvswitch2.11-2.11.0-24.el8fdp
Doc Type:	If docs needed, set a value
Doc Text:
Clone Of:	1737146
Environment:
Last Closed:	2019-11-06 05:22:47 UTC
Target Upstream Version:
Embargoed:

Attachments	(Terms of Use)

Links
System	ID	Private	Priority	Status	Summary	Last Updated
Red Hat Product Errata	RHBA-2019:3720	0	None	None	None	2019-11-06 05:22:59 UTC

Comment 3 Jean-Tsung Hsiao 2019-10-18 14:13:06 UTC

Reproduced with openvswitch2.11-2.11.0-14.el8fdp.
[root@netqe7 ~]# tail -f /var/log/openvswitch/ovs-vswitchd.log
2019-10-18T12:37:22.536Z|01382|bridge|WARN|could not add network device gre0 to ofproto (Address family not supported by protocol)
2019-10-18T12:37:22.555Z|01383|bridge|WARN|could not add network device gre0 to ofproto (Address family not supported by protocol)
2019-10-18T12:37:22.570Z|01384|bridge|WARN|could not add network device gre0 to ofproto (Address family not supported by protocol)
2019-10-18T12:37:22.586Z|01385|bridge|WARN|could not add network device gre0 to ofproto (Address family not supported by protocol)
2019-10-18T12:37:22.606Z|01386|bridge|WARN|could not add network device gre0 to ofproto (Address family not supported by protocol)
2019-10-18T12:37:22.628Z|01387|bridge|WARN|could not add network device gre0 to ofproto (Address family not supported by protocol)
2019-10-18T12:37:22.643Z|01388|bridge|WARN|could not add network device gre0 to ofproto (Address family not supported by protocol)
2019-10-18T12:37:22.663Z|01389|bridge|WARN|could not add network device gre0 to ofproto (Address family not supported by protocol)
2019-10-18T12:37:22.679Z|01390|bridge|WARN|could not add network device gre0 to ofproto (Address family not supported by protocol)
2019-10-18T12:37:22.693Z|01391|bridge|WARN|could not add network device gre0 to ofproto (Address family not supported by protocol)
2019-10-18T12:37:22.713Z|01392|bridge|WARN|could not add network device gre0 to ofproto (Address family not supported by protocol)
2019-10-18T12:37:22.730Z|01393|bridge|WARN|could not add network device gre0 to ofproto (Address family not supported by protocol)
2019-10-18T12:37:22.750Z|01394|bridge|WARN|could not add network device gre0 to ofproto (Address family not supported by protocol)
2019-10-18T12:37:22.765Z|01395|dpif|WARN|Dropped 58 log messages in last 1 seconds (most recently, 0 seconds ago) due to excessive rate
2019-10-18T12:37:22.765Z|01396|dpif|WARN|system@ovs-system: failed to add gre0 as port: Address family not supported by protocol
2019-10-18T12:37:22.765Z|01397|bridge|WARN|could not add network device gre0 to ofproto (Address family not supported by protocol)
2019-10-18T12:37:22.781Z|01398|bridge|WARN|could not add network device gre0 to ofproto (Address family not supported by protocol)
2019-10-18T12:37:22.797Z|01399|bridge|WARN|could not add network device gre0 to ofproto (Address family not supported by protocol)
2019-10-18T12:37:22.813Z|01400|bridge|WARN|could not add network device gre0 to ofproto (Address family not supported by protocol)
2019-10-18T12:37:22.830Z|01401|bridge|WARN|could not add network device gre0 to ofproto (Address family not supported by protocol)
2019-10-18T12:37:22.849

Verified with -18 and -21.

[root@netqe7 yum.repos.d]# ovs-vsctl show
b2cc7db7-4c34-49ee-bb0a-0e97247f04f2
    Bridge "ovsbr0"
        Port "gre0"
            Interface "gre0"
                type: "ip6gre"
                options: {key="123", packet_type="legacy_l2", remote_ip="2001::2"}
        Port "ovsbr0"
            Interface "ovsbr0"
                type: internal
    ovs_version: "2.11.0"
[root@netqe7 yum.repos.d]# rpm -q openvswitch2.11
openvswitch2.11-2.11.0-18.el8fdp.x86_64

NOTE: The verification has been done under Rhel-8.1.0:
[root@netqe7 ~]# uname -r
4.18.0-147.el8.x86_64

Comment 4 Jean-Tsung Hsiao 2019-10-18 15:14:15 UTC

Also, verified with openvswitch2.11-2.11.0-24.el7fdp under 8.0.0:

[root@netqe10 ~]# !25
ovs-vsctl add-br ovsbr0
[root@netqe10 ~]# !28
ovs-vsctl add-port ovsbr0 gre0 -- set interface gre0 type=ip6gre options:key=123 options:packet_type=legacy_l2 options:remote_ip="2001::2"
[root@netqe10 ~]# ovs-vsctl show
438be67b-d765-4db6-8427-802114249252
    Bridge "ovsbr0"
        Port "ovsbr0"
            Interface "ovsbr0"
                type: internal
        Port "gre0"
            Interface "gre0"
                type: "ip6gre"
                options: {key="123", packet_type="legacy_l2", remote_ip="2001::2"}
    ovs_version: "2.11.0"
[root@netqe10 ~]# rpm -q openvswitch2.11
openvswitch2.11-2.11.0-24.el7fdp.x86_64
[root@netqe10 ~]# uname -r
4.18.0-80.el8.x86_64
[root@netqe10 ~]#

Comment 7 errata-xmlrpc 2019-11-06 05:22:47 UTC

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, 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-2019:3720

Note You need to log in before you can comment on or make changes to this bug.