Bug 1745571
| Summary: | [DR][bare metal] Pod hang with container create error | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Tomáš Nožička <tnozicka> |
| Component: | kube-apiserver | Assignee: | Tomáš Nožička <tnozicka> |
| Status: | CLOSED ERRATA | QA Contact: | Xingxing Xia <xxia> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 4.2.0 | CC: | aos-bugs, jokerman, mfojtik, mmccomas, sttts, tnozicka, wsun, xtian, xxia, yinzhou |
| Target Milestone: | --- | ||
| Target Release: | 4.2.0 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | 1714158 | Environment: | |
| Last Closed: | 2019-10-16 06:37:32 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: | 1714158 | ||
|
Comment 1
Tomáš Nožička
2019-08-26 11:43:14 UTC
we need QA to verify it so we can merge the backport Sorry for late. Noticed it, just no enough time/capacity yet on it, due to engaged in other scheduled testings, stories and ON_QA bugs. Will try to verify it this afternoon. Confirmed with payload: 4.2.0-0.nightly-2019-08-31-102058 , can't reproduce the issue. [root@ip-10-0-5-40 ~]# oc get clusterversion NAME VERSION AVAILABLE PROGRESSING SINCE STATUS version 4.2.0-0.nightly-2019-08-31-102058 True False 5h58m Cluster version is 4.2.0-0.nightly-2019-08-31-102058 [root@ip-10-0-5-40 ~]# oc get po -A |grep -v -E "Running|Completed" NAMESPACE NAME READY STATUS RESTARTS AGE [root@ip-10-0-5-40 ~]# oc get co NAME VERSION AVAILABLE PROGRESSING DEGRADED SINCE authentication 4.2.0-0.nightly-2019-08-31-102058 True False False 98m cloud-credential 4.2.0-0.nightly-2019-08-31-102058 True False False 6h19m cluster-autoscaler 4.2.0-0.nightly-2019-08-31-102058 True False False 6h14m console 4.2.0-0.nightly-2019-08-31-102058 True False False 50m dns 4.2.0-0.nightly-2019-08-31-102058 True False False 6h19m image-registry 4.2.0-0.nightly-2019-08-31-102058 True False False 50m ingress 4.2.0-0.nightly-2019-08-31-102058 True False False 164m insights 4.2.0-0.nightly-2019-08-31-102058 True False False 6h20m kube-apiserver 4.2.0-0.nightly-2019-08-31-102058 True False False 6h17m kube-controller-manager 4.2.0-0.nightly-2019-08-31-102058 True False False 6h18m kube-scheduler 4.2.0-0.nightly-2019-08-31-102058 True False False 6h17m machine-api 4.2.0-0.nightly-2019-08-31-102058 True False False 6h19m machine-config 4.2.0-0.nightly-2019-08-31-102058 True False False 158m marketplace 4.2.0-0.nightly-2019-08-31-102058 True False False 3h44m monitoring 4.2.0-0.nightly-2019-08-31-102058 True False False 59m network 4.2.0-0.nightly-2019-08-31-102058 True False False 6h19m node-tuning 4.2.0-0.nightly-2019-08-31-102058 True False False 167m openshift-apiserver 4.2.0-0.nightly-2019-08-31-102058 True False False 21m openshift-controller-manager 4.2.0-0.nightly-2019-08-31-102058 True False False 6h17m openshift-samples 4.2.0-0.nightly-2019-08-31-102058 True False False 6h14m operator-lifecycle-manager 4.2.0-0.nightly-2019-08-31-102058 True False False 6h19m operator-lifecycle-manager-catalog 4.2.0-0.nightly-2019-08-31-102058 True False False 6h19m operator-lifecycle-manager-packageserver 4.2.0-0.nightly-2019-08-31-102058 True False False 21m service-ca 4.2.0-0.nightly-2019-08-31-102058 True False False 6h19m service-catalog-apiserver 4.2.0-0.nightly-2019-08-31-102058 True False False 6h16m service-catalog-controller-manager 4.2.0-0.nightly-2019-08-31-102058 True False False 6h16m storage 4.2.0-0.nightly-2019-08-31-102058 True False False 6h15m 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:2922 |