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):
Steps to Reproduce:
1. Download windows tools
3. right click on oc.exe, look in the details tab
file and product version information is blank (see attached screenshot)
file and product version to be populated with data that can be used to Windows software deployment tooling.
That's what goversioninfo is supposed to be for. It seems the build infrastructure in origin used to handle that, specifically:
This appears not have been moved over to the separate oc repo when it was split out.
Created attachment 1726079 [details]
Screenshot of fixed 4.7 nightly
Just in case QE doesn't have a Windows machine handy, I went to the latest 4.7-nightly, clicked Download the Installer, which takes you to:
Then downloaded and extracted the windows .zip file, and displayed Properties of the included oc.exe. Screenshot attached.
the issue has fixed：
$ ./oc.exe version
Client Version: 4.7.0-0.nightly-2020-11-09-190845
will attach the picture for windows client version .
Created attachment 1727955 [details]
fixed for 4.7 client
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 (Moderate: OpenShift Container Platform 4.7.0 security, bug fix, and enhancement 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.