Description of problem: OpenShift version print not correctly with latest 3.2.1.34 rebuild version Version-Release number of selected component (if applicable): openshift v3.2.1.34 kubernetes v1.2.0-36-g4a3f9c5 etcd 2.2.5 atomic-openshift-3.2.1.34-2.git.20.6367d5d How reproducible: Steps to Reproduce: 1.run `openshift version` on master node 2. 3. Actual results: openshift v3.2.1.34-20-g6367d5d kubernetes v1.2.0-36-g4a3f9c5 etcd 2.2.5 Expected results: openshift v3.2.1.34 kubernetes v1.2.0-36-g4a3f9c5 etcd 2.2.5 Additional info: The issue happened with v3.2.1.34 latest rebuild version atomic-openshift-3.2.1.34-2.git.20.6367d5d
Hi there, I'm moving this into the Command Line Interface component. The Release component doesn't have insight into changing how the version appears, sounds like that's something on the code side of things. I hope this is the right place to move it!
Hi Chuan, Could you clarify what exactly the issue is? The only difference I am seeing is that the version printed in the latest rebuild (v3.2.1.34-20-g6367d5d) has an additional "-20-g6367d5d", and as far as I can tell, this should not be an issue. Thanks
No impacted issues found so far. But the printed version should be consistent with former release.
Moving to installer team. Although I do not believe that this is a bug / issue.
The version inside the binary is minted during the atomic-openshift RPM build process. Moving back to release component.