Bug 1782791
| Summary: | [Enhancement] Missing degraded condition when the static pod installer is unable to create pods due to networking errors | |||
|---|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Michal Fojtik <mfojtik> | |
| Component: | kube-apiserver | Assignee: | Michal Fojtik <mfojtik> | |
| Status: | CLOSED ERRATA | QA Contact: | Ke Wang <kewang> | |
| Severity: | low | Docs Contact: | ||
| Priority: | low | |||
| Version: | 4.4 | CC: | aos-bugs, eparis, mfojtik, scuppett, xxia | |
| Target Milestone: | --- | Keywords: | UpcomingSprint | |
| Target Release: | 4.5.0 | |||
| Hardware: | Unspecified | |||
| OS: | Unspecified | |||
| Whiteboard: | ||||
| Fixed In Version: | Doc Type: | No Doc Update | ||
| Doc Text: | Story Points: | --- | ||
| Clone Of: | 1775252 | |||
| : | 1782793 (view as bug list) | Environment: | ||
| Last Closed: | 2020-07-13 17:12:38 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: | ||||
| Bug Blocks: | 1764629, 1775252, 1782793, 1782795 | |||
|
Comment 2
Xingxing Xia
2019-12-16 08:41:57 UTC
Refer to bugs 1775252 and 1764629,
When the static pod installer is unable to create pods due to networking errors, and forced rotate kubeapiserver. waited for several minutes(> 5minutes), still unable to get the status value changing to ‘True’.
$ date; oc get kubeapiserver cluster -o yaml | grep -B 2 -E 'InstallerPodNetworkingDegraded|InstallerPodContainerWaitingDegraded'
Tue 14 Jan 2020 12:34:30 PM CST
- lastTransitionTime: "2020-01-14T03:12:17Z"
status: "False"
type: InstallerPodContainerWaitingDegraded
- lastTransitionTime: "2020-01-14T01:34:01Z"
status: "False"
type: InstallerPodNetworkingDegraded
Xingxing Xia can you please retest? If this won't work now, can you please capture the installer pod YAML (to check whether the status in the pod carry the reason why it is stucked). OK, will leave to my colleague Ke Wang to retest this. I'll retest bug 1775252, the 4.3 version of this bug. 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-2020:2409 |