Bug 1416763

Summary: virt-manager GUI, select ISO screen
Product: [Fedora] Fedora Reporter: Michal Schorm <mschorm>
Component: virt-managerAssignee: Cole Robinson <crobinso>
Status: CLOSED DEFERRED QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 25CC: berrange, crobinso, virt-maint
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-02-05 20:54:17 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
from left top to right bottom none

Description Michal Schorm 2017-01-26 11:18:00 UTC 
Created attachment 1244726 [details]
from left top to right bottom

I believe, there is a wrong GUI window in the process of creating new VM from ISO.

See the attachement:
1) top left corner:
   click "new VM"
2) select "provide ISO", select "use ISO image" and "select ISO image from teh computer"
3) >> THIS IS THE ODD SCREEN <<
   it offers you to select THE EXISTING VM-DISK IMAGE FOR IMPORT, wich is nonsense, however, you can click "search local"
4) now you are in the right "window", you find and select your desired ISO and proceed



The window 3 should not appear, the button should lead directly to window 4.
It is really really confusing.
Comment 1 Cole Robinson 2017-02-05 20:54:17 UTC 
Yes the screen is confusing but we haven't really figured out a way to work around it.

That screen is a front end for libvirt's 'storage APIs' which allow connecting to and enumerating all types of different storage config: plain directory, nfs, iscsi, lvm, gluster, ceph, etc. By default, the only thing it's going to show is the default image directory, so it will show your existing disk images which is definitely odd for a cdrom. But someone might use a gluster share as their CDROM media directory, so we need to enable accessing those locations, and this was the best we could come up with.

So baring any new idea I don't expect this to change