Bug 1659185

Summary: virt-manager throws error when trying to use rbd volumes for importing VM into libvirt
Product: [Fedora] Fedora Reporter: Neal Gompa <ngompa13>
Component: virt-managerAssignee: Cole Robinson <crobinso>
Status: CLOSED CURRENTRELEASE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 29CC: berrange, crobinso, ngompa13
Target Milestone: ---   
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: 2019-03-26 21:20:27 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
Screenshot demonstrating virt-manager error
none
Screenshot showing the Ceph storage pool none

Description Neal Gompa 2018-12-13 18:59:55 UTC
Created attachment 1514171 [details]
Screenshot demonstrating virt-manager error

Description of problem:
When trying to import a VM into libvirt through virt-manager that is stored as an RBD volume, virt-manager sets and invalid path and fails to create, saying it doesn't exist.

Version-Release number of selected component (if applicable):
1.6.0-1.3.git3bc7ff24c.fc29

How reproducible:
Always

Steps to Reproduce:
1. Open Create VM wizard
2. Select import from disk
3. Select volume from RBD pool
4. Try to have it create the VM

Actual results:
Fails with error: "Cannot create storage pool: Cannot open directory '/home/ngompa/rbd/ReactOSVM': No such file or directory"

Expected results:
VM creation is successful and I can boot a VM from Ceph.

Additional info:

Screenshot demonstrating the error is attached.

Comment 1 Neal Gompa 2018-12-13 19:02:30 UTC
Created attachment 1514172 [details]
Screenshot showing the Ceph storage pool

Comment 2 Cole Robinson 2018-12-13 19:46:28 UTC
Thanks for the report. Can you try virt-manager 2.0.0 from updates testing? it had some fixes in this area