Bug 1497819 - Broker should not rely on image field of APB yaml
Summary: Broker should not rely on image field of APB yaml
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Service Broker
Version: 3.7.0
Hardware: All
OS: All
unspecified
low
Target Milestone: ---
: 3.7.0
Assignee: David Zager
QA Contact: Jian Zhang
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-10-02 18:42 UTC by David Zager
Modified: 2017-11-28 22:14 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
undefined
Clone Of:
Environment:
Last Closed: 2017-11-28 22:14:33 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2017:3188 0 normal SHIPPED_LIVE Moderate: Red Hat OpenShift Container Platform 3.7 security, bug, and enhancement update 2017-11-29 02:34:54 UTC

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 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


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