Red Hat Bugzilla – Bug 1500934
When broker is deployed to a namespace other than ansible-service-broker, secret lookup fails
Last modified: 2018-04-05 05:30:13 EDT
Description of problem: The secret lookup is hardcoded to the ansible-service-broker namespace. It needs to be dynamically loaded so that the broker can be deployed to arbitrary namespaces Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
https://github.com/openshift/ansible-service-broker/pull/482
Which method of deploy asb? By template or by ansible installer? Could you provide a reproduce steps? Thanks.
Fabian, Could you provide a reproduce steps? Thanks.
John, this card lack enough info to verify for QE, could you help confirm and provide? Thanks.
To test: 1. Install and deploy the broker to a namespace other than ansible-service-broker, for example openshift-ansible-service-broker (which is where the openshift-ansible installer would put it) 2. Create a secret named testsecret containing postgresql_user: test postgresql_password: testpass 3. Add a secrets section to the broker config containing: secrets: - apb_name: dh-rhscl-postgresql-apb secret: test title: test (if you aren't pulling the apbs from dockerhub you may need to change the apb_name to match what is in y our broker) 4. Attempt to deploy the rhscl-postgresql-apb If the deployment doesn't fail with an error saying that the secret wasn't found in the ansible-service-broker namespace then it worked
I will verify after BZ https://bugzilla.redhat.com/show_bug.cgi?id=1496426 is merged.
Verified and passed. Testing base on steps in comment6 with latest image v3.7.0-0.189.0.0
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:0636