Bug 1498185

Summary:	[RFE] Move versioning label onto APB spec
Product:	OpenShift Container Platform	Reporter:	Dylan Murray <dymurray>
Component:	Service Broker	Assignee:	Dylan Murray <dymurray>
Status:	CLOSED ERRATA	QA Contact:	Zhang Cheng <chezhang>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	3.7.0	CC:	aos-bugs, dymurray, dzager
Target Milestone:	---
Target Release:	3.7.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	No Doc Update
Doc Text:	undefined	Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-04-05 09:29:37 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 Dylan Murray 2017-10-03 16:20:21 UTC

Description of problem:
This bug is to track the movement from checking the APB spec version on the label and instead expecting APB developers to declare the version in apb.yml itself.

Actual results:
Version is declared in the "com.redhat.apb.version" label on the image.

Expected results:
Version is declared in apb.yml and encoded into "com.redhat.apb.spec" label.

Comment 1 Dylan Murray 2017-10-03 17:30:42 UTC

https://github.com/ansibleplaybookbundle/ansible-playbook-bundle/pull/129

Comment 2 Dylan Murray 2017-10-03 17:31:03 UTC

https://github.com/openshift/ansible-service-broker/pull/468

Comment 3 David Zager 2017-10-04 15:51:12 UTC

https://github.com/ansibleplaybookbundle/rhscl-mariadb-apb/pull/3
https://github.com/ansibleplaybookbundle/mediawiki123-apb/pull/5
https://github.com/ansibleplaybookbundle/rhscl-postgresql-apb/pull/4
https://github.com/ansibleplaybookbundle/rhscl-mysql-apb/pull/2

Comment 6 Zhang Cheng 2017-10-17 01:27:46 UTC

Verified and passed by QE. Thanks.

Comment 10 errata-xmlrpc 2018-04-05 09:29:37 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/RHBA-2018:0636