Bug 1701806
Summary: | sdn pod CrashLoopBackOff after running sometime | ||
---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | Wang Haoran <haowang> |
Component: | Networking | Assignee: | Casey Callendrello <cdc> |
Status: | CLOSED ERRATA | QA Contact: | Meng Bo <bmeng> |
Severity: | medium | Docs Contact: | |
Priority: | unspecified | ||
Version: | 3.11.0 | CC: | aos-bugs, bbennett, weliang |
Target Milestone: | --- | ||
Target Release: | 3.11.z | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2019-06-26 09:08:06 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: |
Description
Wang Haoran
2019-04-22 03:00:38 UTC
workaround is delete the ovs and sdn pod, and let it recreated. Install new cluster using v3.11.117, wait cluster running for several hours, do not see sdn pod CrashLoopBackOff 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:1605 |