Bug 1654948 - Asb version in stage registry v3.11.43-2 is not right
Summary: Asb version in stage registry v3.11.43-2 is not right
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Service Broker
Version: 3.11.0
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: 3.11.z
Assignee: Jason Montleon
QA Contact: Zihan Tang
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-11-30 06:56 UTC by Zihan Tang
Modified: 2019-01-10 09:05 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-01-10 09:04:12 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2019:0024 0 None None None 2019-01-10 09:05:49 UTC

Description Zihan Tang 2018-11-30 06:56:31 UTC 
Description of problem:
The ASB image in v3.11.43-2 is not right
# docker run --entrypoint=asbd registry...../ose-ansible-service-broker:v3.11.43-2 --version
1.4.1

it should use version '1.3.20' release package.

Version-Release number of selected component (if applicable):
v3.11.43-2

How reproducible:
always

Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:
using version '1.3.20' release package in ASB 3.11 image.

Additional info:
Comment 4 Zihan Tang 2018-12-21 09:48:46 UTC 
I find this issue has been fixed in the latest errata: 
asb image is right
docker run --entrypoint=asbd .../openshift3/ose-ansible-service-broker:v3.11.59-2 --version
1.3.21

So change the bug to ON_QA.
Comment 6 Zihan Tang 2018-12-26 02:42:58 UTC 
According to #comment4, image in tag v3.11.59-2 is correct. Move to Verified.
Comment 8 errata-xmlrpc 2019-01-10 09:04:12 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-2019:0024
Note You need to log in before you can comment on or make changes to this bug.