@Jeff, The current fix as below, version of service-catalog is using image tag. Is it intended? Why not keep to use SC self record to trace as usual? Such as: v0.1.14 # docker run --entrypoint=service-catalog brew-pulp-docker01.web.prod.ext.phx2.redhat.com:8888/openshift3/ose-service-catalog:v3.10.0-0.20.0.0 --version v3.10.0-0.20.0
It is intended. I understand that it's not ideal and am working on trying to figure out a way to make it known what upstream version of catalog has been built for OCP.
I added additional version information that includes both the git tag and the upstream version. Should be in the next rebuild.
@Jeff, that is great! The upstream is very important for QE and user. Thanks.
Changing status to ON_QA since downstream image is ready for test.
Verified and thanks. # service-catalog --version v3.10.0-0.21.0;Upstream:v0.1.13
Unsure if this will satisfy the PR checker with the bug tracker bot: Fixed in: https://github.com/openshift/service-catalog/commit/6338d88f9725ecf5755737de6c46f2008a4f4733
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:1816