Bug 1379775 - there is no 4.0.3 vdsm errata
Summary: there is no 4.0.3 vdsm errata
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: releng
Version: 4.0.2
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: ---
Assignee: Joey Boggs
QA Contact: Entitlement Bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-09-27 16:00 UTC by Marina Kalinin
Modified: 2016-09-27 20:36 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-09-27 19:52:44 UTC
oVirt Team: Integration
Target Upstream Version:

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

Description Marina Kalinin 2016-09-27 16:00:34 UTC 
If I understand correctly, there vdsm 4.0.3 released. But I cannot find related errata.

Starting here:
https://access.redhat.com/errata/RHEA-2016:1671.html

Clicking on the "Updated Packages" tab.
It says - 
"Note: More recent versions of these packages may be available. Click a package name for more details. "

Clicking on 
vdsm-4.18.11-1.el7ev.x86_64.rpm

It brings me here:
https://access.redhat.com/downloads/content/rhel---7/x86_64/5132/vdsm/4.18.11-1.el7ev/x86_64/fd431d51/package

And I do not see any latest package released in the drop box on top.

For additional information on errata system: see bz#1379772.
Comment 2 Marina Kalinin 2016-09-27 18:45:23 UTC 
The main question is whether there was vdsm 4.0.3 or no. And the current vdsm release is the only available vdsm in 4.0 today.
Comment 3 Dan Kenigsberg 2016-09-27 19:52:44 UTC 
Bugzilla is not aware of any vdsm bug for ovirt-4.0.3.

https://bugzilla.redhat.com/buglist.cgi?bug_status=CLOSED&component=vdsm&list_id=5951200&product=Red%20Hat%20Enterprise%20Virtualization%20Manager&query_format=advanced&target_milestone=ovirt-4.0.3

git show v4.18.11
git show v4.18.12

in upstream agree: there was no update to vdsm in 4.0.3
Note You need to log in before you can comment on or make changes to this bug.