Bug 1784469

Summary:	[Kuryr]Pod is stuck in container creating after installation
Product:	OpenShift Container Platform	Reporter:	Luis Tomas Bolivar <ltomasbo>
Component:	Networking	Assignee:	Luis Tomas Bolivar <ltomasbo>
Networking sub component:	kuryr	QA Contact:	Jon Uriarte <juriarte>
Status:	CLOSED ERRATA	Docs Contact:
Severity:	high
Priority:	medium	CC:	bbennett, gcheresh, itbrown, ltomasbo, nagrawal, oblaut, wsun
Version:	4.3.0	Keywords:	Triaged
Target Milestone:	---
Target Release:	4.3.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:	1781198	Environment:
Last Closed:	2020-01-23 11:19:28 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:	1781198
Bug Blocks:

Comment 2 Jon Uriarte 2019-12-24 10:05:04 UTC

Verified in 4.3.0-0.nightly-2019-12-23-120031 on 2019-12-06.2 OSP 13 puddle.

The OCP installer finishes successfully:

 $ oc get clusterversion
 NAME      VERSION                             AVAILABLE   PROGRESSING   SINCE   STATUS
 version   4.3.0-0.nightly-2019-12-23-120031   True        False         13h     Cluster version is 4.3.0-0.nightly-2019-12-23-120031


New pods can be created successfully:

 $ oc create -f https://raw.githubusercontent.com/openshift/origin/master/examples/hello-openshift/hello-pod.json
 pod/hello-openshift created

 $ oc get pods
 NAME              READY   STATUS    RESTARTS   AGE
 hello-openshift   1/1     Running   0          77s

 $ oc delete -f https://raw.githubusercontent.com/openshift/origin/master/examples/hello-openshift/hello-pod.json
 pod "hello-openshift" deleted

 $ oc get pods
 No resources found in default namespace.

Comment 4 errata-xmlrpc 2020-01-23 11:19:28 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-2020:0062