Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1081569

Summary: [Admin Portal] Sorting in 'Install Host' dialog lists older isos first
Product: Red Hat Enterprise Virtualization Manager Reporter: Jiri Belka <jbelka>
Component: ovirt-engine-webadmin-portalAssignee: Ravi Nori <rnori>
Status: CLOSED CURRENTRELEASE QA Contact: Pavel Stehlik <pstehlik>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 3.2.0CC: aberezin, acathrow, bazulay, ecohen, emesika, gklein, iheim, jbelka, Rhev-m-bugs, rnori, yeylon
Target Milestone: ---   
Target Release: 3.4.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: infra
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-04-07 14:13:10 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Infra RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
screenshot none

Description Jiri Belka 2014-03-27 15:17:18 UTC 
Created attachment 879523 [details]
screenshot

Description of problem:
There's incorrect sorting in 'Install Host' dialog, older iso is displayed before newer iso.

rhev-hypervisor6-6.5-20131202.0.3.2.el6_5.noarch
rhev-hypervisor6-6.5-20140225.0.3.2.el6_5.noarch

See screenshot.

Version-Release number of selected component (if applicable):
rhevm-3.2.6-0.50.el6ev.noarch

How reproducible:
100%

Steps to Reproduce:
1. have various versions of rhev-hypervisor6 installed on rhevm
2. check admin portal for 'Install Host' dialog
3.

Actual results:
the list is sorted numerically

Expected results:
reversed order, newest first

Additional info:
Comment 1 Ravi Nori 2014-03-31 14:41:42 UTC 
I am working with 3.4 upstream and I see proper sorting in Install dialog. Please check with latest 3.4

contents of my directory
ovirt-node-iso-3.0.4-1.0.20131202.0.3.2.vdsm34beta3.el6.iso
ovirt-node-iso-3.0.4-1.0.20140225.0.3.2.vdsm34beta3.el6.iso
ovirt-node-iso-3.0.4-1.0.20140325.0.3.2.vdsm34beta3.el6.iso
ovirt-node-iso-3.0.5-1.0.20131202.0.3.2.vdsm34beta3.el6.iso

is sorted as
ovirt-node-iso-3.0.5-1.0.20131202.0.3.2.vdsm34beta3.el6.iso
ovirt-node-iso-3.0.4-1.0.20140325.0.3.2.vdsm34beta3.el6.iso
ovirt-node-iso-3.0.4-1.0.20140225.0.3.2.vdsm34beta3.el6.iso
ovirt-node-iso-3.0.4-1.0.20131202.0.3.2.vdsm34beta3.el6.iso
Comment 2 Barak 2014-04-06 11:54:09 UTC 
This bug was opened on 3.2

I assume we have fixed it probably for 3.3,

Please double check and if done please CLOSE CURRENTRELEASE
Comment 3 Jiri Belka 2014-04-07 08:39:37 UTC 
Yes it is for 3.2. Not worth to repair in 3.2? It's OK in 3.3.
Comment 4 Ravi Nori 2014-04-07 14:13:10 UTC 
Fixed in 3.3