Bug 1389700 - RFE: don't allow user to add the same usb stick for twice
Summary: RFE: don't allow user to add the same usb stick for twice
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Virtualization Tools
Classification: Community
Component: virt-manager
Version: unspecified
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Cole Robinson
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-10-28 09:27 UTC by lnie
Modified: 2019-06-15 17:55 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-06-15 17:55:14 UTC

Attachments (Terms of Use)
journal from guest machine (183.75 KB, text/x-vhdl)
2016-10-28 09:27 UTC, lnie 		no flags Details
journal from host machine (1.37 MB, text/x-vhdl)
2016-10-28 09:28 UTC, lnie 		no flags Details
screenshot (80.75 KB, image/png)
2016-10-28 09:29 UTC, lnie 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Description lnie 2016-10-28 09:27:25 UTC 
Created attachment 1214901 [details]
journal from guest machine

Description of problem:


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

virt-manager-1.4.0-3.fc25.noarch

How reproducible:
always

Steps to Reproduce:
1.add the usb stick to the virtual machine using virt-manager
2.plug out it from the host machine and insert it again
3.try to add the usb stick to the virtual machine 

Actual results:
please see the attached screenshot

Expected results:
  

Additional info:
Comment 1 lnie 2016-10-28 09:28:23 UTC 
Created attachment 1214913 [details]
journal from host machine
Comment 2 lnie 2016-10-28 09:29:07 UTC 
Created attachment 1214914 [details]
screenshot
Comment 3 Cole Robinson 2016-12-13 17:17:57 UTC 
Makes sense to me, moving to the upstream tracker
Comment 4 Cole Robinson 2019-06-15 17:55:14 UTC 
I tested this and nowadays libvirt already rejects it for us at VM startup, so I think it's solved at that layer
Note You need to log in before you can comment on or make changes to this bug.