Hide Forgot
Description of problem: The cluster version is 4.1.9, but the output of `service-catalog --version` is `v4.1.8`. See below: mac:~ jianzhang$ oc get clusterversion NAME VERSION AVAILABLE PROGRESSING SINCE STATUS version 4.1.9 True False 176m Cluster version is 4.1.9 mac:~ jianzhang$ oc rsh apiserver-dns94 sh-4.2# service-catalog --version v4.1.8;Upstream:v0.1.42 mac:~ jianzhang$ oc -n openshift-service-catalog-controller-manager rsh controller-manager-kwfsr sh-4.2# service-catalog --version v4.1.8;Upstream:v0.1.42 Version-Release number of selected component (if applicable): Service Catalog version: io.openshift.build.commit.id=1dd02c427d9a0b143e5f2a6ef05506a79a311c13 io.openshift.build.commit.url=https://github.com/openshift/service-catalog/commit/1dd02c427d9a0b143e5f2a6ef05506a79a311c13 io.openshift.build.source-location=https://github.com/openshift/service-catalog Service Catalog operator version: io.openshift.build.commit.id=a898d5daab55b3eadcd96a00a7b17f89856bd35b io.openshift.build.commit.url=https://github.com/openshift/cluster-svcat-apiserver-operator/commit/a898d5daab55b3eadcd96a00a7b17f89856bd35b io.openshift.build.source-location=https://github.com/openshift/cluster-svcat-apiserver-operator How reproducible: always Steps to Reproduce: 1. Install the 4.1.9 OCP. 2. Enable the Service Catalog. 3. Check the Service Catalog version. Actual results: The output of `service-catalog --version` is `v4.1.8`. Expected results: The output of `service-catalog --version` should be `v4.1.9`. Additional info:
This commit points out that we are printing the VERSION constant from the version.go file https://github.com/openshift/service-catalog/commit/cf2f161c3107ae9af0b365957db853b4c52985f1 The comment on version states "// VERSION is the version string for built artifacts. It's set by the build system, and should // not be changed in this codebase" https://github.com/openshift/service-catalog/blob/master/pkg/version.go#L24-L26 Sounds like something in the build process isn't updating that for the 4.1.9 release.
Hi, Jesus Many thanks for your explanation! I got it. Encounter this issue again, move on it to the ART team per comment 1. mac:~ jianzhang$ oc -n openshift-service-catalog-apiserver exec apiserver-4brcs -- service-catalog --version v4.1.10;Upstream:v0.1.42 mac:~ jianzhang$ oc get clusterversion NAME VERSION AVAILABLE PROGRESSING SINCE STATUS version 4.1.11 True False 127m Cluster version is 4.1.11
Hi, Luke Yes, thanks! It fixed now, verify it. Details: mac:~ jianzhang$ oc exec apiserver-8jxtx -- service-catalog --version v4.1.16;Upstream:v0.1.42 mac:~ jianzhang$ oc get clusterversion NAME VERSION AVAILABLE PROGRESSING SINCE STATUS version 4.1.0-0.nightly-2019-09-10-183945 True False 33m Cluster version is 4.1.0-0.nightly-2019-09-10-183945 I think this payload "4.1.0-0.nightly-2019-09-10-183945" is 4.1.15+, so the v4.1.16 is right.
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:2768