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

Bug 1637010

Summary: Multiple namespaces while provision fails
Product: OpenShift Container Platform Reporter: Piotr Kliczewski <pkliczew>
Component: Service BrokerAssignee: Todd Sanders <tsanders>
Status: CLOSED NOTABUG QA Contact: Zihan Tang <zitang>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 3.11.0CC: aos-bugs, chezhang, jiazha, jmatthew, jmontleo, pkliczew, rhallise
Target Milestone: ---   
Target Release: 3.11.z   
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: 2018-10-22 12:42:59 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:
Bug Depends On:    
Bug Blocks: 1608837    

Description Piotr Kliczewski 2018-10-08 13:00:39 UTC
We saw BZ #1570603 where the provision was restarted many times. We still can see many namespaces as specified in BZ #1608837.

Comment 1 John Matthews 2018-10-08 16:17:29 UTC
How is the automation broker being deployed?

We defaulted to _not_ keep the transient namespace on errors to avoid this issue in OCP 3.11.  

The change was tracked in below BZ to openshift-ansible as well as the APB which deploys the broker through oc cluster up

https://bugzilla.redhat.com/show_bug.cgi?id=1618547#c5


Below is the change submitted for openshift-ansible:
  https://github.com/openshift/openshift-ansible/pull/9977/files

and the same change for the APB which would be used if deploying with oc cluster up:
  https://github.com/openshift/ansible-service-broker/pull/1075/files



Heart of issue is on any error the Service Catalog will continue to call the Broker and repeat the operation...eventually stepping back on the number of calls, but a large number (on order of hundreds/thousands perhaps will happen in a day or two).  The API doesn't yet have a way for the Broker to report an error and not be retried.

Comment 2 Jason Montleon 2018-10-08 18:28:29 UTC
I could not reproduce this with a a 3.11 openshift-ansible install. As John mentioned we defaulted this to false in 3.11:
https://github.com/openshift/openshift-ansible/blob/release-3.11/roles/ansible_service_broker/defaults/main.yml#L17

Can you please tell us what method you used to install and provide the inventory for openshift-ansible if applicable.

Comment 3 Piotr Kliczewski 2018-10-10 07:24:13 UTC
Ryan, Please provide details how we deploy the broker.

Comment 4 Ryan Hallisey 2018-10-22 12:42:59 UTC
it's deployed with keep namespaces on error.   Flag should be turned off in the config file.