Bug 1962590 - [SCALE] segfault with ovnkube adding to address set
Summary: [SCALE] segfault with ovnkube adding to address set
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Networking
Version: 4.8
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: 4.7.z
Assignee: Federico Paolinelli
QA Contact: Anurag saxena
Depends On: 1958958
TreeView+ depends on / blocked
Reported: 2021-05-20 10:27 UTC by OpenShift BugZilla Robot
Modified: 2021-06-29 04:20 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
Clone Of:
Last Closed: 2021-06-29 04:19:46 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Github openshift ovn-kubernetes pull 546 0 None open [release-4.7] Bug 1962590: NewAddressSet: return nil in case of error 2021-06-10 01:03:29 UTC
Red Hat Product Errata RHBA-2021:2502 0 None None None 2021-06-29 04:20:01 UTC

Comment 3 OpenShift Automated Release Tooling 2021-06-17 12:29:08 UTC
OpenShift engineering has decided to not ship Red Hat OpenShift Container Platform 4.7.17 due a regression https://bugzilla.redhat.com/show_bug.cgi?id=1973006. All the fixes which were part of 4.7.17 will be now part of 4.7.18 and planned to be available in candidate channel on June 23 2021 and in fast channel on June 28th.

Comment 5 Mike Fiedler 2021-06-18 02:56:53 UTC
Verified on 4.7.0-0.nightly-2021-06-17-075632.  The cluster was 300 nodes, but we could not scale it to 15K pods on 4.7.   The scalability fixes in 4.8 have really helped in that area.   In 4.7 we could not scale beyond 7500 pods before nodes started going NotReady and pod startup latencies grew exponentially.

But, at 300 nodes and 7500 running pods, no segfaults/SIGSEGV were seen in ovnkube-master.

Comment 8 errata-xmlrpc 2021-06-29 04:19:46 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 (OpenShift Container Platform 4.7.18 bug fix 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.


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