+++ This bug was initially created as a clone of Bug #1891555 +++ Created attachment 1724192 [details] screenshot of the lack of version info on the oc.exe windows binary Description of problem: The oc.exe tool for windows does not have version meta-data imbeded in it. This makes automated deployment/management of it very difficult in an enterprise setting. Version-Release number of selected component (if applicable): 4.4.23 How reproducible: Every time Steps to Reproduce: 1. Download windows tools 2. install 3. right click on oc.exe, look in the details tab Actual results: file and product version information is blank (see attached screenshot) Expected results: file and product version to be populated with data that can be used to Windows software deployment tooling. Additional info: --- Additional comment from yselkowi on 2020-10-26 16:20:17 UTC --- That's what goversioninfo is supposed to be for. It seems the build infrastructure in origin used to handle that, specifically: https://github.com/openshift/origin/blob/master/hack/lib/constants.sh#L198-L259 https://github.com/openshift/origin/blob/master/hack/lib/build/binaries.sh#L218-L221 https://github.com/openshift/origin/blob/master/hack/lib/build/binaries.sh#L238-L240 This appears not have been moved over to the separate oc repo when it was split out.
This is waiting in the queue for its turn.
PR in the queue.
Build the oc with the PR , could see the file and product version to be populated with SOURCE_GIT_TAG=4.6.99.
Created attachment 1750399 [details] oc detail
Created attachment 1752757 [details] detail
Download the oc from payload: https://openshift-release-artifacts.apps.ci.l2s4.p1.openshiftapps.com/4.6.0-0.nightly-2021-01-30-211400/, could see the oc version like https://bugzilla.redhat.com/show_bug.cgi?id=1891892#c7. will move to verified status.
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 (Important: OpenShift Container Platform 4.6.16 security and bug fix update), 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/RHSA-2021:0308