Description of problem: You cannot use an extracted oc to extract oc Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: 1. oc adm release extract --command oc <any release image> 2../oc adm release extract --command oc <any release image> Actual results: The second extract fails Expected results: An extracted oc should be able to extract another oc
I have [1] in flight touching this same code. Might want to wait on verifying this bug until that settles. [1]: https://github.com/openshift/oc/pull/165
Confirmed with latest version, the issue has fixed: [root@dhcp-140-138 tmp]# oc adm release extract --command oc registry.svc.ci.openshift.org/ocp/release:4.3.0-0.nightly-2019-11-17-145435 [root@dhcp-140-138 tmp]# ll total 81424 -rwxr-xr-x. 1 root root 83377816 Nov 15 21:55 oc [root@dhcp-140-138 tmp]# ./oc version Client Version: 4.3.0-0.nightly-2019-11-17-145435 [root@dhcp-140-138 test2]# ../oc adm release extract --command oc registry.svc.ci.openshift.org/ocp/release:4.3.0-0.nightly-2019-11-13-173334 [root@dhcp-140-138 test2]# ./oc version Client Version: 4.3.0-0.nightly-2019-11-13-173334
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-2020:0062