Bug 1098766 - ovirt-node-iso builds on the download site all have the same internal ID
Summary: ovirt-node-iso builds on the download site all have the same internal ID
Keywords:
Status: CLOSED DUPLICATE of bug 1087118
Alias: None
Product: oVirt
Classification: Retired
Component: ovirt-node
Version: 3.4
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: Fabian Deutsch
QA Contact: bugs@ovirt.org
URL: http://resources.ovirt.org/releases/s...
Whiteboard: node
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-05-18 08:38 UTC by Evgheni Dereveanchin
Modified: 2014-05-19 02:24 UTC (History)
8 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2014-05-19 02:24:46 UTC
oVirt Team: ---
Embargoed:


Attachments (Terms of Use)

Description Evgheni Dereveanchin 2014-05-18 08:38:40 UTC
Description of problem:
on the community website there are several ISO builds with different names:
http://resources.ovirt.org/releases/stable/iso/

ovirt-node-iso-3.0.4-1.0.201401291204.vdsm34.el6.iso
ovirt-node-iso-3.4-20140410.0.el6.iso
ovirt-node-iso-3.4-20140423.0.el6.iso

When downloading the last two ISOs, internally they are identified as version 3.0.4-1.0.201401291204.el6 which prohibits for example correct node updates (reinstall is proposed instead, since internal versions match)

Version-Release number of selected component (if applicable):
3.0.4

How reproducible:
Always

Steps to Reproduce:
1. download ovirt-node-iso-3.4-20140410.0.el6.iso
2. install hypervisor
3. download ovirt-node-iso-3.4-20140423.0.el6.iso
4. try to upgrade previously installed hypervisor using the newer ISO

Actual results:
version 3.0.4-1.0.201401291204.el6 displayed by the bootloader of both ISOs as well as in the node TUI. Upgrade not possible, reinstall proposed

Expected results:
unique versions matching ISO name are listed by the bootloader. Upgrade works as expected.

Comment 1 haiyang,dong 2014-05-19 02:24:46 UTC

*** This bug has been marked as a duplicate of bug 1087118 ***


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