Bug 1962590
Summary: | [SCALE] segfault with ovnkube adding to address set | ||
---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | OpenShift BugZilla Robot <openshift-bugzilla-robot> |
Component: | Networking | Assignee: | Federico Paolinelli <fpaoline> |
Networking sub component: | ovn-kubernetes | QA Contact: | Anurag saxena <anusaxen> |
Status: | CLOSED ERRATA | Docs Contact: | |
Severity: | high | ||
Priority: | unspecified | CC: | aconstan, astoycos, dcbw, fpaoline, mifiedle |
Version: | 4.8 | ||
Target Milestone: | --- | ||
Target Release: | 4.7.z | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | No Doc Update | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2021-06-29 04:19:46 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | 1958958 | ||
Bug Blocks: |
Comment 3
OpenShift Automated Release Tooling
2021-06-17 12:29:08 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. 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. https://access.redhat.com/errata/RHBA-2021:2502 |