Bug 1444458

Summary: [RFE] Create VM, Operating System Chooser shows "BSD" and "Debian" as first options
Product: Red Hat Enterprise Virtualization Manager Reporter: Andreas Stolzenberger <astolzen>
Component: ovirt-engine-dashboardAssignee: Vojtech Szocs <vszocs>
Status: CLOSED DUPLICATE QA Contact: Pavel Stehlik <pstehlik>
Severity: high Docs Contact:
Priority: medium    
Version: 4.1.0CC: dfediuck, michal.skrivanek, mtessun, tjelinek
Target Milestone: ---Keywords: FutureFeature
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: 2018-04-23 09:31:54 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Virt RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
OS choosers first choices when none

Description Andreas Stolzenberger 2017-04-21 11:22:27 UTC
Created attachment 1273303 [details]
OS choosers first choices when

Description of problem:
When creating a new VM in the RHV Gui and selecting "Operating System", the OS chooser showns stuf like "Debian 7" and "Free BSD" as first choice. 

You need to scroll far down to get "RHEL 7"


Version-Release number of selected component (if applicable):
4.1.1.6-0.1.el7

How reproducible:
Create VM, click on "Operating System"

Expected results:
The list should show "RHEL 7" as first option, followed by "RHEL 6", CentOS and maybe different flavours of Windows.

Please resort this list and move important and frequently used stuff towards the top and stuff like "BSD", "Debian" or "RHEL 3" to the far end of the list.


Additional info:

Comment 1 Yaniv Kaul 2018-04-22 06:16:46 UTC
Please triage.

Comment 2 Martin Tessun 2018-04-23 08:37:18 UTC
From my pov it is reasonable to have the Red Hat products first in the scrolldown list.

Afaik we also discussed a more generic approach as we are having more OSes to handle.

With that we should address this together with BZ 1341161.

Any idea on the effort and timeline these two could be addressed?

Cheers,
Martin

Comment 3 Michal Skrivanek 2018-04-23 09:31:54 UTC
I would squash that with 1341161. It's not yet targeted though

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

Comment 4 Franta Kust 2019-05-16 13:09:29 UTC
BZ<2>Jira Resync