Bug 1950407
| Summary: | network kube-rbac-proxy scripts crashloop rather than non-crash looping | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | OpenShift BugZilla Robot <openshift-bugzilla-robot> |
| Component: | Networking | Assignee: | Dan Winship <danw> |
| Networking sub component: | openshift-sdn | QA Contact: | zhaozhanqi <zzhao> |
| Status: | CLOSED ERRATA | Docs Contact: | |
| Severity: | high | ||
| Priority: | unspecified | CC: | aconstan, oarribas, wking |
| Version: | 4.6 | ||
| Target Milestone: | --- | ||
| Target Release: | 4.6.z | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: |
Cause: At install time, the sdn pods were not correctly dealing with the partially-installed state of the cluster, and could end up repeatedly crashing and being restarted until other parts of the install had completed.
Consequence: Kubelet will put the crashing pods into "CrashLoopBackoff", and wait longer and longer before restarting them after each crash, eventually causing the installation process to stall for, eg, 10 minutes, while waiting for the sdn pods to come back, resulting in a noticeably slower installation process. (The install should still succeed, it's just slower than expected.)
Fix: The sdn pods now correctly check the cluster state and wait until the install has reached a point where they can proceed.
Result: The pods do not crash, so there are no restarts and no delays.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2021-05-12 12:18:10 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: | 1885002 | ||
| Bug Blocks: | |||
|
Comment 3
zhaozhanqi
2021-05-06 03:20:53 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.6.28 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:1487 |