Bug 1745571 - [DR][bare metal] Pod hang with container create error
Summary: [DR][bare metal] Pod hang with container create error
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: kube-apiserver
Version: 4.2.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: 4.2.0
Assignee: Tomáš Nožička
QA Contact: Xingxing Xia
URL:
Whiteboard:
Depends On:
Blocks: 1714158
TreeView+ depends on / blocked
 
Reported: 2019-08-26 11:40 UTC by Tomáš Nožička
Modified: 2019-10-16 06:37 UTC (History)
10 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1714158
Environment:
Last Closed: 2019-10-16 06:37:32 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2019:2922 0 None None None 2019-10-16 06:37:45 UTC

Comment 1 Tomáš Nožička 2019-08-26 11:43:14 UTC 
cluster-kube-apiserver-operator has library-go from 1eb1131507bff6d494f05b23c8ecf850836d7328

git merge-base --is-ancestor 06b95bad6b48b5b8b1095e22c19e4bf42505f4c7 1eb1131507bff6d494f05b23c8ecf850836d732
Comment 3 Tomáš Nožička 2019-08-29 14:25:03 UTC 
we need QA to verify it so we can merge the backport
Comment 4 Xingxing Xia 2019-08-30 04:47:19 UTC 
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.
Comment 6 zhou ying 2019-09-02 08:36:30 UTC 
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
Comment 7 errata-xmlrpc 2019-10-16 06:37:32 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, 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
Note You need to log in before you can comment on or make changes to this bug.