Description of problem: virtctl version id not align for client and server Client Version: version.Info{GitVersion:"v0.9.3", GitCommit:"2f54966f09376152585818f0b50e0b03b5badc71", GitTreeState:"clean", BuildDate:"2018-11-05T16:43:35Z", GoVersion:"go1.9.4", Compiler:"gc", Platform:"linux/amd64"} Server Version: version.Info{GitVersion:"v1.3.0-10-1-g5173ad6", GitCommit:"2f54966f09376152585818f0b50e0b03b5badc71", GitTreeState:"clean", BuildDate:"2018-11-06T16:11:54Z", GoVersion:"go1.9.4", Compiler:"gc", Platform:"linux/amd64"} Version-Release number of selected component (if applicable): v1.3.0-10 Expected results: Both Client and Server have the same version on d
Marc and I spoke about this. The issue is that the rpm is getting the version differently than the container. This is not ciritical IMHO, we plan to fix it for 1.4.
Fix already provided for the latest builds in 1.4. It's good for tests.
verified with latest 1.4 build: $ virtctl version Client Version: version.Info{GitVersion:"v0.12.0-alpha.0", GitCommit:"ba61019514707956f5f601bda39c93280a458200", GitTreeState:"clean", BuildDate:"2018-12-13T16:47:10Z", GoVersion:"go1.10.3", Compiler:"gc", Platform:"linux/amd64"} Server Version: version.Info{GitVersion:"v0.12.0-alpha.2", GitCommit:"cd09f01644f33f91e70901ed4cc51d62fb48741e", GitTreeState:"clean", BuildDate:"2018-12-19T06:08:03Z", GoVersion:"go1.10.3", Compiler:"gc", Platform:"linux/amd64"}
1.4 is bases on 0.13.0 virtctl version Client Version: version.Info{GitVersion:"v0.13.0", GitCommit:"f6a440c81b74a47259aa3697763e91bc19e6e663", GitTreeState:"clean", BuildDate:"2019-01-15T14:40:55Z", GoVersion:"go1.10.3", Compiler:"gc", Platform:"linux/amd64"} Server Version: version.Info{GitVersion:"v0.13.0", GitCommit:"f6a440c81b74a47259aa3697763e91bc19e6e663", GitTreeState:"clean", BuildDate:"2019-01-15T14:43:23Z", GoVersion:"go1.10.3", Compiler:"gc", Platform:"linux/amd64"}
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/RHEA-2019:0418