Bug 1414085 – change versioning schema for rhevm-appliance

Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.

Bug 1414085 - change versioning schema for rhevm-appliance

Summary:	change versioning schema for rhevm-appliance

Status:	CLOSED ERRATA

Aliases:	None

Product:	Red Hat Enterprise Virtualization Manager
Classification:	Red Hat
Component:	rhevm-appliance (Show other bugs)
Sub Component:
Version:	unspecified
Hardware:	Unspecified Unspecified

Priority	urgent Severity medium
Target Milestone:	ovirt-4.1.0-rc
Target Release:	---
Assigned To:	Ryan Barry
QA Contact:	Gonza
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2017-01-17 12:18 EST by Sandro Bonazzola
Modified:	2017-04-24 21:12 EDT (History)
CC List:	4 users (show)

See Also:
Fixed In Version:	rhvm-appliance-4.1.20170120.1-1.el7ev.
Doc Type:	Release Note
Doc Text:	Previously the name of the “rhevm-appliance” RPM contained only a timestamp, without versioning information. In this release, the Red Hat Virtualization release will now be included in the name of the “rhevm-appliance” RPM and will be visible from the node channel.
Story Points:	---
Clone Of:
Environment:
Last Closed:
Type:	Bug
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	Node
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

External Trackers
Tracker	ID	Priority	Status	Summary	Last Updated
Red Hat Product Errata	RHEA-2017:1066	normal	SHIPPED_LIVE	rhvm-appliance bug fix and enhancement update for RHV 4.1	2017-04-18 17:03:07 EDT

Groups: None (edit)

Description Sandro Bonazzola 2017-01-17 12:18:22 EST

Description of problem:
Currently all the appliance builds from 3.6, 4.0, 4.1 are versionedusing timestamp.
So an upgrade from 20161211 to 20170117 may result in a downgrade to 3.6.
Previously it wasn't an issue since we didn't put the appliance in the node channel but now we need proper versioning.

We need to bump epoch and start numbering with <version>.<timestamp> or equivalent.

Comment 1 Fabian Deutsch 2017-01-17 12:26:00 EST

I'd suggest to use the naming scheme of the rhvh next image - or wrapper rpm

Comment 2 Gonza 2017-02-02 10:42:38 EST

Verified with:
rhvm-appliance-4.1.20170126.0-1.el7ev.noarch.rpm

Comment 3 Gonza 2017-03-01 04:14:13 EST

Verified also with:
rhevm-appliance-4.0.20170227.0-1.el7ev.noarch.rpm

Note You need to log in before you can comment on or make changes to this bug.