Bug 1612876 - Issues with "oc cluster add automation-service-broker"
Summary: Issues with "oc cluster add automation-service-broker"
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Service Broker
Version: 3.10.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: 4.1.0
Assignee: Jason Montleon
QA Contact: Zhang Cheng
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-08-06 12:54 UTC by Mauricio Magnani
Modified: 2022-03-13 15:21 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-11-26 17:02:21 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Mauricio Magnani 2018-08-06 12:54:39 UTC
### Description of problem ###

OpenShift v3.10 Client "oc cluster add automation-service-broker" should install openshift3/ose-ansible-service-broker v3.10. Instead, it currently installs the latest release of the upstream automation broker.

### Version-Release number ###

RHEL 7.5 host with Openshift v3.10 Linux Client installed

### business impact ### 

Current behavior makes it difficult for developers using "oc cluster up" or cdk to test APBs because the version of the service broker they are using for test is significantly different from the production version included with OCP v3.10.

Comment 1 Jason Montleon 2018-08-13 19:57:22 UTC
As a temporary workaround you should be able to patch the dc to get a similar broker:

oc patch dc -n openshift-automation-service-broker openshift-automation-service-broker --patch='{"spec":{"template":{"spec":{"containers":[{"name": "penshift-automation-service-broker", "image":"ansibleplaybookbundle/origin-ansible-service-broker:release-1.2"}]}}}}'

PR's for 3.11 and 3.10:
https://github.com/openshift/origin/pull/20626
https://github.com/openshift/origin/pull/20627

Comment 2 Charles Moulliard 2018-08-14 07:49:40 UTC
We can't apply the patch on origin 3.10 as the openshift ansible role installing ASB uses the following namespace : openshift-ansible-service-broker and not openshift-automation-service-broker and container name is asb and not penshift-automation-service-broker

Comment 3 Jason Montleon 2018-08-14 12:40:32 UTC
Hi Charles

If you're using openshift-ansible you should be able to change the image and tag using these options
ansible_service_broker_image_prefix
ansible_service_broker_image_tag

Regardless you should be able to modify the patch line to work similarly, something alone the lines of:
oc patch dc -n openshift-ansible-service-broker asb --patch='{"spec":{"template":{"spec":{"containers":[{"name": "asb", "image":"ansibleplaybookbundle/origin-ansible-service-broker:release-1.2"}]}}}}'

If you're using openshift-ansible and still having problems, or the default behavior is not as expected, please open a bug against openshift-anisble so we can track that issue appropriately and get it fixed.

Comment 8 John Matthews 2018-08-30 17:06:12 UTC
Aligning to 4.0 to investigate further.

Comment 9 John Matthews 2018-11-26 17:02:21 UTC
Closing this BZ as 'oc cluster up' will not be part of OCP 4.0.


Note You need to log in before you can comment on or make changes to this bug.