Bug 1416009

Summary:	[Upstream ONLY] VDSM package is inconsistent between upstream and downstream
Product:	[oVirt] vdsm	Reporter:	cshao <cshao>
Component:	Packaging.rpm	Assignee:	Lev Veyde <lveyde>
Status:	CLOSED NOTABUG	QA Contact:	cshao <cshao>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	4.19.2	CC:	bugs, cshao, dguo, huzhao, jiawu, qiyuan, sbonazzo, weiwang, yaniwang, ycui, yzhao
Target Milestone:	ovirt-4.1.0-rc	Flags:	rule-engine: ovirt-4.1+ cshao: testing_ack+
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-01-31 09:18:56 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 cshao 2017-01-24 11:01:22 UTC

Description of problem:
VDSM package is inconsistent between upstream and downstream

Upstream:
vdsm-4.19.2-1.el7.centos.x86_64 (ovirt-node-ng-4.1.0-0.20170124.0+1)

Downstream:
vdsm-4.19.2-2.el7ev.x86_64 (rhvh-4.1-0.20170120.0+1)

Version-Release number of selected component (if applicable):
ovirt-node-ng-installer-ovirt-4.1-pre-2017012404.iso
imgbased-0.9.5-0.201701181504git35ef6dc.el7.centos.noarch

How reproducible:
100%

Steps to Reproduce:
1. Install ovirt-node-ng-installer-ovirt-4.1-pre-2017012404.iso.
2. Check vdsm version.
3. Compare the difference between downstream and upstream.

Actual results:
VDSM package is inconsistent between upstream and downstream

Expected results:
Should keep the same vdsm version between upstream and downstream.



Additional info:

Comment 1 Ryan Barry 2017-01-24 13:53:07 UTC

The most recent version of vdsm in resources.ovirt.org is 2-1

Looks like this needs an updated publish upstream.

Comment 2 Red Hat Bugzilla Rules Engine 2017-01-24 13:53:14 UTC

Target release should be placed once a package build is known to fix a issue. Since this bug is not modified, the target version has been reset. Please use target milestone to plan a fix for a oVirt release.

Comment 3 Sandro Bonazzola 2017-01-31 09:18:56 UTC

release tag can't be the same upstream and downstream, there's no guarantee they'll be the same. Closing as not a bug.