Bug 765771 - when adding removable device, don't require storage path to be speficied
Summary: when adding removable device, don't require storage path to be speficied
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Virtualization Tools
Classification: Community
Component: virt-manager
Version: unspecified
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
Assignee: Cole Robinson
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-12-09 11:32 UTC by David Jaša
Modified: 2014-07-06 19:31 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-02-07 21:51:59 UTC

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

Description David Jaša 2011-12-09 11:32:05 UTC 
Description of problem:
SSIA.

Version-Release number of selected component (if applicable):
virt-manager-0.9.0-7.el6.x86_64

How reproducible:
always

Steps to Reproduce:
1. go to VM properties -> Add hardware -> Storage
2. choose "Select managed or other existing storage"
3. choose "Device type" as "IDE cdrom" or "Floppy disk"
4. hit "finish"
  
Actual results:
error "A storage path must be specified" pops up

Expected results:
empty CDROM/Floppy device is added

Additional info:
Comment 1 Cole Robinson 2011-12-09 21:39:45 UTC 
Not urgent, and given reduced capacity for virt-manager/virtinst, just moving this to the upstream tracker. Particularly that the user could still attach a device pointing to any disk path and simply 'eject' the media later to get an empty device.
Comment 2 Cole Robinson 2012-02-07 21:51:59 UTC 
Fixed upstream:

http://git.fedorahosted.org/git?p=virt-manager.git;a=commit;h=101d328ed6917838b49ba825e7b2c77254cf4d64
Note You need to log in before you can comment on or make changes to this bug.