Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1498185 - [RFE] Move versioning label onto APB spec
[RFE] Move versioning label onto APB spec
Status: CLOSED ERRATA
Product: OpenShift Container Platform
Classification: Red Hat
Component: Service Broker (Show other bugs)
3.7.0
Unspecified Unspecified
unspecified Severity unspecified
: ---
: 3.7.0
Assigned To: Dylan Murray
Zhang Cheng
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2017-10-03 12:20 EDT by Dylan Murray
Modified: 2018-04-05 05:30 EDT (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: No Doc Update
Doc Text:
undefined
Story Points: ---
Clone Of:
Environment:
Last Closed: 2018-04-05 05:29:37 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2018:0636 None None None 2018-04-05 05:30 EDT

  None (edit)
Description Dylan Murray 2017-10-03 12:20:21 EDT
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 6 Zhang Cheng 2017-10-16 21:27:46 EDT
Verified and passed by QE. Thanks.
Comment 10 errata-xmlrpc 2018-04-05 05:29:37 EDT
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

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