Bug 1570065

Summary: Ansible Service Broker fails to deploy due to missing namespace argument
Product: OpenShift Container Platform Reporter: Leif Madsen <lmadsen>
Component: Service BrokerAssignee: Fabian von Feilitzsch <fabian>
Status: CLOSED ERRATA QA Contact: Jian Zhang <jiazha>
Severity: high Docs Contact:
Priority: high    
Version: 3.9.0CC: aos-bugs, jiazha, jmatthew
Target Milestone: ---   
Target Release: 3.9.z   
Hardware: All   
OS: All   
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-06-27 18:01:34 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:

Description Leif Madsen 2018-04-20 14:54:36 UTC
Description of problem:

Ansible Service Broker will fail to deploy properly on OpenShift 3.9 using openshift-ansible due to a missing configuration option in the ConfigMap for the broker-config.

Version-Release number of selected component (if applicable): v3.9 latest

How reproducible: Always

Steps to Reproduce:
1. deploy service catalog and ansible service broker from openshift-ansible release-3.9
2. see po/asb-1-<random> fail due to inability to pull secret from '' namespace

Actual results:

Fails to deploy due to missing namespace argument.

Expected results:

Deploy without error :)

Additional info:

PR in upstream available at https://github.com/openshift/openshift-ansible/pull/8063

Comment 1 John Matthews 2018-04-26 22:09:20 UTC

Please ensure this is fixed in 3.10, I saw the PR was submitted for release-3.9, unsure if we need another change in master as well.

Comment 2 Fabian von Feilitzsch 2018-04-27 12:47:28 UTC
This is already fixed in 3.10, it was just never backported to 3.9 until pr#8063. Going to realign to 3.9.z and set status to ON_QA since the change has been merged into the release 3.9 branch.

Comment 5 errata-xmlrpc 2018-06-27 18:01:34 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.