Bug 1627473 - Address issue of failed deprovisions resulting in potentially hundreds of transient namespaces being created.
Summary: Address issue of failed deprovisions resulting in potentially hundreds of tra...
Keywords:
Status: CLOSED DUPLICATE of bug 1649076
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Service Broker
Version: 3.11.0
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: 3.11.z
Assignee: Jesus M. Rodriguez
QA Contact: Zihan Tang
URL:
Whiteboard:
Depends On: 1628235
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-09-10 16:35 UTC by John Matthews
Modified: 2019-03-25 13:28 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1618547
Environment:
Last Closed: 2019-03-25 13:28:36 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1628235 0 unspecified CLOSED Service Catalog establishes a new connection for every request and never closes them. 2022-03-13 15:33:08 UTC

Internal Links: 1628235

Comment 1 John Matthews 2018-09-10 16:38:02 UTC 
Recap of issue:

In 3.11.0 we will be deleting a failed namespace to reduce potential for spamming a cluster and creating hundreds of namespaces on failed deprovisions.  

In 3.11.z we would like to go back to previous behavior of keeping transient namespace around on failures to help aid debugging.  

This BZ is tracking work to address how we can handle service-catalog calling the broker in a loop on failed deprovisions.
Comment 2 John Matthews 2018-09-12 14:11:44 UTC 
Service Catalog bz possibly related

Bug 1628235 - Service Catalog establishes a new connection for every request and never closes them.
Comment 3 Shawn Hurley 2019-03-25 13:28:36 UTC 
This bug is fixed by deleting the failed namespaces and to go back to the previous behavior is an RFE being tracked in the duplicate bug. 

Closing in favor of more correct bug title.

*** This bug has been marked as a duplicate of bug 1649076 ***
Note You need to log in before you can comment on or make changes to this bug.