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

Bug 1497819

Summary: Broker should not rely on image field of APB yaml
Product: OpenShift Container Platform Reporter: David Zager <dzager>
Component: Service BrokerAssignee: David Zager <dzager>
Status: CLOSED ERRATA QA Contact: Jian Zhang <jiazha>
Severity: low Docs Contact:
Priority: unspecified    
Version: 3.7.0CC: aos-bugs, chezhang, smunilla
Target Milestone: ---   
Target Release: 3.7.0   
Hardware: All   
OS: All   
Whiteboard:
Fixed In Version: Doc Type: No Doc Update
Doc Text:
undefined
 Story Points: ---
Clone Of: Environment:
Last Closed: 2017-11-28 22:14:33 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 2017-10-02 18:42:33 UTC 
Description of problem:

Currently, the Ansible Service Broker relies on the image field of the apb.yml to determine the image to used for Ansible Playbook Bundle execution. Instead, the broker should generate the fully qualified path to the image and use that path on APB execution.

Version-Release number of selected component (if applicable):

N/A


Steps to Reproduce:
1. Start Ansible Service Broker in OpenShift Origin cluster (w/ service catalog)
2. Examine the apb spec stored in etcd

Actual results:

Image field of stored specs are equivalent to image field from loaded apb's apb.yml (example: ansibleplaybookbundle/pyzip-demo-db-apb:latest)


Expected results:

Image field should be the fully qualified path (example: docker.io/ansibleplaybookbundle/pyzip-demo-db-apb:latest)
Comment 1 David Zager 2017-10-02 18:45:58 UTC 
https://github.com/openshift/ansible-service-broker/pull/433
Comment 2 David Zager 2017-10-04 15:10:26 UTC 
https://github.com/ansibleplaybookbundle/ansible-playbook-bundle/pull/121
Comment 7 errata-xmlrpc 2017-11-28 22:14:33 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/RHSA-2017:3188