Bug 1464486

Summary:	[RFE] Align versioning schema with upstream
Product:	Red Hat Enterprise Virtualization Manager	Reporter:	Sandro Bonazzola <sbonazzo>
Component:	rhevm-appliance	Assignee:	Yuval Turgeman <yturgema>
Status:	CLOSED ERRATA	QA Contact:	Pavol Brilla <pbrilla>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	4.1.4	CC:	apinnick, dfediuck, eheftman, grafuls, lsvaty, mgoldboi, pstehlik, sbonazzo, yturgema
Target Milestone:	ovirt-4.2.0	Keywords:	FutureFeature
Target Release:	---	Flags:	pstehlik: testing_plan_complete-
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Enhancement
Doc Text:	Previously, the version tag was used as part of the RPM's naming scheme, for example, "4.1.timestamp", which created differences between the upstream and downstream versioning schemes. In this release, the downstream versioning scheme is aligned with the upstream scheme and the timestamp has moved from the version tag to the release tag.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-05-15 19:00:03 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	Node	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Sandro Bonazzola 2017-06-23 14:18:16 UTC

Downstream we have:
  rhvm-appliance-4.1.20170621.0-1.el7.noarch.rpm
while upstgream we have:
  ovirt-engine-appliance-4.1-20170622.1.el7.centos.noarch.rpm

Please align downstream versioning schema with upstream.

Comment 2 Sandro Bonazzola 2017-06-23 14:20:08 UTC

For reference, having different versioing schema leads to bugs like bug #1464461 where the test on the appliance version fails because upstream it's detected like version "4.1" while downstream is detected ad "4.1.20170621.0".

Comment 7 Pavol Brilla 2017-11-08 12:36:43 UTC

Comparison on lastest provided builds:

	rhvm-appliance-4.1.20171102.0-1.el7.noarch.rpm

	rhvm-appliance-4.2-20171102.0.el7.noarch.rpm

Comment 12 errata-xmlrpc 2018-05-15 19:00:03 UTC

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/RHSA-2018:1525

Comment 13 Franta Kust 2019-05-16 13:05:16 UTC

BZ<2>Jira Resync