Bug 1445504
| Summary: | sentry: nil panic in pkg/sdn/plugin/pod.go", line 228, in UpdateLocalMulticastRules | |||
|---|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Ben Bennett <bbennett> | |
| Component: | Networking | Assignee: | Dan Williams <dcbw> | |
| Status: | CLOSED ERRATA | QA Contact: | Meng Bo <bmeng> | |
| Severity: | high | Docs Contact: | ||
| Priority: | unspecified | |||
| Version: | 3.5.0 | CC: | aos-bugs, hongli, smunilla | |
| Target Milestone: | --- | |||
| Target Release: | --- | |||
| Hardware: | Unspecified | |||
| OS: | Unspecified | |||
| Whiteboard: | ||||
| Fixed In Version: | Doc Type: | Bug Fix | ||
| Doc Text: |
Cause: The initialization order of the SDN plugin sets the event handler up too late.
Consequence: Early events have no handler so the SDN panics
Fix: Re-order the SDN initialization so the event handler is in place before it can ever be called
Result: No more panics
|
Story Points: | --- | |
| Clone Of: | ||||
| : | 1445505 (view as bug list) | Environment: | ||
| Last Closed: | 2017-08-10 05:21:25 UTC | Type: | Bug | |
| 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: | ||||
| Bug Blocks: | 1445505 | |||
|
Description
Ben Bennett
2017-04-25 20:04:48 UTC
do regression testing on atomic-openshift-3.6.94-1.git.0.ba4aad2.el7.x86_64 and no issue found. and the node log at startup as below: Jun 05 05:32:13 atomic-openshift-node[2657]: I0605 05:32:13.575439 2657 node.go:236] Waiting for kubelet network plugin initialization Jun 05 05:32:14 atomic-openshift-node[2657]: I0605 05:32:14.121589 2657 node.go:269] Starting openshift-sdn pod manager Jun 05 05:32:14 atomic-openshift-node[2657]: I0605 05:32:14.149582 2657 node.go:292] openshift-sdn network plugin ready 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/RHEA-2017:1716 |