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

Bug 1542235

Summary:	APB cannot be provisioned more than once in same namespace
Product:	OpenShift Container Platform	Reporter:	David Zager <dzager>
Component:	Service Broker	Assignee:	David Zager <dzager>
Status:	CLOSED ERRATA	QA Contact:	Zhang Cheng <chezhang>
Severity:	low	Docs Contact:
Priority:	unspecified
Version:	3.9.0	CC:	aos-bugs, chezhang, dzager, jesusr, jiazha, jmatthew, mburke, zhsun, zitang
Target Milestone:	---
Target Release:	3.11.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	No Doc Update
Doc Text:	undefined	Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-10-11 07:19:06 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 David Zager 2018-02-05 21:27:58 UTC

Description of problem:

Currently, when a user selects an APB (PostgreSQL for example) to provision, the user is asked which project the APB should be provisioned into. However, since the deployment(config)'s, services, routes, etc. are of the form 'hello-world' (simple) or 'postgresql-$version-$apb_plan_id' (complex), only one can be provisioned/managed per namespace.



How reproducible: Always


Steps to Reproduce:
1. (Starting with an OpenShift Cluster + Service Catalog + Service Broker) Provision postgresql-apb into 'testproject' (dev plan + version 9.6)
2. Provision postgresql-apb again into 'testproject' (dev plan + version 9.6)
3. Get deploymentconfigs in the 'testproject' namespace

Actual results:

Only one deploymentconfig listed


Expected results:

Two deploymentconfigs listed

Comment 1 Zhang Cheng 2018-02-06 02:25:34 UTC

David, which is the target release

Comment 2 John Matthews 2018-02-16 16:24:59 UTC

Moving to 3.10 as we have concerns of properly addressing this in regard to update operations.  Worried we may destabilize 3.9 at this point.

Comment 3 John Matthews 2018-04-27 19:46:01 UTC

Didn't get to this in a safe time in 3.10 work cycle.  I don't want to introduce larger changes to APBs with ~2+ weeks to code freeze.

Moving to 3.11, we plan to address this when refactor the example APBs for galaxy integration.

Comment 4 David Zager 2018-08-02 12:58:52 UTC

https://errata.devel.redhat.com/advisory/33505 updated

openshift-enterprise-mariadb-apb-v3.11.0-0.10.0.3
openshift-enterprise-mediawiki-apb-v3.11.0-0.10.0.3
openshift-enterprise-postgresql-apb-v3.11.0-0.10.0.3
openshift-enterprise-mysql-apb-v3.11.0-0.10.0.3
openshift-enterprise-mediawiki-container-v3.11.0-0.10.0.0
openshift-enterprise-asb-container-v3.11.0-0.10.0.1
openshift-enterprise-apb-base-container-v3.11.0-0.10.0.3

Comment 5 Zhang Cheng 2018-08-03 06:59:07 UTC

Verified and Passed.

Test coverage: https://polarion.engineering.redhat.com/polarion/#/project/OSE/workitems/testcase?query=trello%3A5vybIGku

Comment 6 Michael Burke 2018-09-13 20:08:13 UTC

If this issue should be in the 3.11 release notes, can you add some doc text? It is not clear to me what the fix is.

Comment 7 Jesus M. Rodriguez 2018-09-13 21:45:33 UTC

(In reply to Michael Burke from comment #6)
> If this issue should be in the 3.11 release notes, can you add some doc
> text? It is not clear to me what the fix is.

I removed the requires_doc_text flag. It does not need to be in the release notes.

Comment 9 errata-xmlrpc 2018-10-11 07:19:06 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-2018:2652