Red Hat Bugzilla – Bug 1542235
APB cannot be provisioned more than once in same namespace
Last modified: 2018-10-11 03:19:41 EDT
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
David, which is the target release
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.
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.
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
Verified and Passed. Test coverage: https://polarion.engineering.redhat.com/polarion/#/project/OSE/workitems/testcase?query=trello%3A5vybIGku
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.
(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.
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