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

Bug 1654948

Summary:	Asb version in stage registry v3.11.43-2 is not right
Product:	OpenShift Container Platform	Reporter:	Zihan Tang <zitang>
Component:	Service Broker	Assignee:	Jason Montleon <jmontleo>
Status:	CLOSED ERRATA	QA Contact:	Zihan Tang <zitang>
Severity:	high	Docs Contact:
Priority:	high
Version:	3.11.0	CC:	aos-bugs, chezhang, dyan, jfan, jiazha, jmatthew, jmontleo, lmeyer, wsun
Target Milestone:	---
Target Release:	3.11.z
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-01-10 09:04:12 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 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