Bug 1118756

Summary: RFE: storage: gluster: support vol-download and vol-upload
Product: [Community] Virtualization Tools Reporter: Peter Krempa <pkrempa>
Component: libvirtAssignee: Libvirt Maintainers <libvirt-maint>
Status: CLOSED DEFERRED QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: unspecifiedCC: crobinso, dyuan, mzhan, virt-bugs, weizhan, xuzhang
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: 1079173 Environment:
Last Closed: 2020-11-03 17:00:29 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:
Bug Depends On: 1079173    
Bug Blocks:    

Description Peter Krempa 2014-07-11 13:12:29 UTC 
+++ This bug was initially created as a clone of Bug #1079173 +++

Description of problem:
Libvirt's storage backend driver for gluster volumes doesn't support volume upload/download

Version-Release number of selected component (if applicable):
libvirt-1.2.6-1.el7.x86_64

How reproducible:
100%

Steps to Reproduce:
# virsh vol-list gluster-pool
Name                 Path                                    
-----------------------------------------
rh.img               gluster://xx.xx.xx.xx/gluster-vol1/rh.img

# virsh vol-download rh.img /tmp/tt.
tt.img  tt.xml  
[root@4-196 virt-test]# virsh vol-download rh.img /tmp/tt.download --pool gluster-pool
error: cannot download from volume rh.img
error: this function is not supported by the connection driver: storage pool doesn't support volume download
Comment 2 Daniel Berrangé 2020-11-03 17:00:29 UTC 
Thank you for reporting this issue to the libvirt project. Unfortunately we have been unable to resolve this issue due to insufficient maintainer capacity and it will now be closed. This is not a reflection on the possible validity of the issue, merely the lack of resources to investigate and address it, for which we apologise. If you none the less feel the issue is still important, you may choose to report it again at the new project issue tracker https://gitlab.com/libvirt/libvirt/-/issues The project also welcomes contribution from anyone who believes they can provide a solution.