Description of problem: Unexpected and/or mismatched versions when downloading openshift client from mirror.openshift.com Version-Release number of the following components: n/a How reproducible: Always Steps to Reproduce: 1. 2. 3. Actual results: $ curl https://mirror.openshift.com/pub/openshift-v4/clients/ocp/latest /openshift-client-linux-4.2.9.tar.gz -o openshift-client-linux-4.2.9.tar.gz | tar zxvf - oc $ ./oc version Client Version: openshift-clients-4.2.2-201910250432 $ export VERSION=$(curl -s https://mirror.openshift.com/pub/openshift-v4/clients/ocp-dev-preview/latest/release.txt | grep 'Name:' | awk -F: '{print $2}' | xargs) $ echo $VERSION 4.4.0-0.nightly-2019-12-06-144548 $ curl -s https://mirror.openshift.com/pub/openshift-v4/clients/ocp-dev-preview/$VERSION/openshift-client-linux-$VERSION.tar.gz | tar zxvf - oc oc $ ./oc version Client Version: openshift-clients-4.3.0-201910250623-91-gc994341a Expected results: Additional info:
This may be an ART time problem (not running oc adm release extract after they relabel the payload).
In this space (but not this issue) is extract-time version injection into the installer: bug 1773257. > ...not running oc adm release extract after they relabel the payload... It's hard to see how payload-relabels would work without a fresh extraction, because the installers from the old extraction wouldn't pin the relabeled release image. But maybe there's some magic that bumps installer pullspec pins without also getting oc version injection?
> ... not running oc adm release extract after they relabel the payload ... Also in this space, extract-time version injection only landed in oc with 4.3, so there's no extract-time oc manipulation in these 4.2 release images. If we want that, we'd have to backport bug 1715001, which eventually resulted in [1,2,3,4] landing in 4.3. [1]: https://github.com/openshift/oc/pull/88 [2]: https://github.com/openshift/oc/pull/131 [3]: https://github.com/openshift/oc/pull/155 [4]: https://github.com/openshift/oc/pull/198
*** Bug 1781909 has been marked as a duplicate of this bug. ***
*** Bug 1786837 has been marked as a duplicate of this bug. ***
*** Bug 1788357 has been marked as a duplicate of this bug. ***
The LifecycleStale keyword was removed, because the needinfo? flag was reset or the bug received blocker/security keyword. The bug assignee was notified.
This bug hasn't had any activity 7 days after it was marked as LifecycleStale, so we are closing this bug as WONTFIX. If you consider this bug still valuable, please reopen it or create new bug.
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days