Bug 1401847

Summary:	OpenShift version format should be like v3.4.0.32, not v3.4.0.32+d349492
Product:	OpenShift Container Platform	Reporter:	Weihua Meng <wmeng>
Component:	Installer	Assignee:	Troy Dawson <tdawson>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Johnny Liu <jialiu>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	3.4.0	CC:	aos-bugs, gpei, jokerman, mmccomas, tdawson, wmeng
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:
Clones:	1413839 (view as bug list)		Environment:
Last Closed:	2016-12-20 14:39:43 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Weihua Meng 2016-12-06 09:06:31 UTC

Description of problem:
OpenShift version format should be like v3.4.0.32, should not have extra string.
We should keep OpenShift version format consistency.

Version-Release number of selected component (if applicable):
openshift v3.4.0.32+d349492

How reproducible:
Always

Steps to Reproduce:
1. check OpeShift version from image openshift3/ose:latest
# docker run --rm openshift3/ose:latest version


Actual results:
openshift v3.4.0.32+d349492

Expected results:
openshift v3.4.0.32

Additional info:
1. The OpenShift version format is not like this before.
openshift v3.4.0.32+d349492
openshift v3.4.0.21+ca4702d
openshift v3.4.0.10
openshift v3.3.1.7
openshift v3.2.2.2

Comment 1 Scott Dodson 2016-12-06 16:05:33 UTC

Can you confirm that everything installs and functions properly even with the additional information in the version? If so then we'll leave this Upcomingrelease.

Comment 2 Weihua Meng 2016-12-06 16:13:39 UTC

Yes. latest openshift-ansible can handle it correctly even with extra string.

TASK [openshift_version : set_fact] ********************************************
Tuesday 06 December 2016  08:21:07 +0000 (0:00:29.580)       0:02:26.112 ******
ok: [ec2-54-90-215-179.compute-1.amazonaws.com] => {"ansible_facts": {"openshift_version": "3.4.0.32+d349492"}, "changed": false}
 
TASK [openshift_version : set_fact] ********************************************
Tuesday 06 December 2016  08:21:07 +0000 (0:00:00.188)       0:02:26.300 ******
ok: [ec2-54-90-215-179.compute-1.amazonaws.com] => {"ansible_facts": {"openshift_version": "3.4.0.32"}, "changed": false}
 
TASK [openshift_version : set_fact] ********************************************
Tuesday 06 December 2016  08:21:07 +0000 (0:00:00.156)       0:02:26.457 ******
ok: [ec2-54-90-215-179.compute-1.amazonaws.com] => {"ansible_facts": {"openshift_image_tag": "v3.4.0.32"}, "changed": false}

Comment 3 Troy Dawson 2016-12-19 21:42:36 UTC

Fixed with this pull request
https://github.com/openshift/ose/pull/514
It was not fixed upstream.  This is an OCP bug only.

This has been merged into ocp and is in OCP v3.4.0.38 or newer.

Comment 4 Weihua Meng 2016-12-20 01:48:20 UTC

it is fixed. 
both rpm and image are fine now.
docker run --rm openshift3/ose:latest version
openshift v3.4.0.38
will move it to VERIFIED once ON-QA.

Comment 5 Troy Dawson 2016-12-20 14:19:05 UTC

Moving to ON_QA.
Since this has never gone to customers, I will not be attaching it to an errata.

Comment 6 Weihua Meng 2016-12-20 14:23:02 UTC

Verified.
both rpm and image are fine now.
openshift v3.4.0.38

Comment 7 Troy Dawson 2016-12-20 14:39:43 UTC

Since this was never released to customers, I am marking this CLOSED.