Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1723143

Summary:	[kuryr]Recreation of the same app with the same project after deletion
Product:	OpenShift Container Platform	Reporter:	Itzik Brown <itbrown>
Component:	Networking	Assignee:	Maysa Macedo <mdemaced>
Networking sub component:	kuryr	QA Contact:	GenadiC <gcheresh>
Status:	CLOSED ERRATA	Docs Contact:
Severity:	high
Priority:	high	CC:	asegurap, bbennett, jschluet, ltomasbo, mdemaced, slinaber, zzhao
Version:	3.11.0	Keywords:	Triaged, ZStream
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:		Environment:
Last Closed:	2019-10-16 06:32:20 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Itzik Brown 2019-06-23 08:27:00 UTC

Description of problem:
Creating a project , then creating an app, deleting the project and then repeat the process cause the pod to be stuck in ContainerCreating status.

Version-Release number of selected component (if applicable):
2019-03-19.1
docker-registry.engineering.redhat.com/rhosp14/openstack-kuryr-cni             latest              8727fff71b96        5 days ago          521 MB
docker-registry.engineering.redhat.com/rhosp14/openstack-kuryr-controller      latest              553b6f72cb4b        5 days ago          476 MB

How reproducible:

Steps to Reproduce:
1.oc new-project hello
2.oc new-app openshift/hello-openshift
3.oc delete project hello
4.oc new-project hello
5.oc new-app openshift/hello-openshift
6.oc get pod -> Verify the pod is stuck in ContainerCreating status 

Actual results:


Expected results:


Additional info:

Comment 3 Steve Linabery 2019-08-14 13:53:44 UTC

I don't see a backport to stable/rocky, and there is no downstream build containing the patch in the upstream gerrit reviews, so I am moving this back to ON_DEV. MODIFIED means we have a fix in a build, and I don't see that here; please correct me if I'm wrong.

Comment 5 Ben Bennett 2019-09-10 12:34:21 UTC

@Maysa if this has been fixed anywhere other than master, please clone this bug and set the target release appropriately.  Thanks.

Comment 7 Itzik Brown 2019-10-06 08:28:03 UTC

4.2.0-0.nightly-2019-10-02-122541

Comment 8 errata-xmlrpc 2019-10-16 06:32:20 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