Description of problem: See https://bugzilla.redhat.com/show_bug.cgi?id=1002320#c7 >> Ok, then, is17. >> >> But it would be nice to have recursive upload. I can imagine it would be >> useful to upload VMs from other data domain etc... > > Please open a RFE about it. We can think about adding that support in a future > release. Version-Release number of selected component (if applicable): is22 How reproducible: 100% Steps to Reproduce: 1. 2. 3. Actual results: engine-image-uploader could not do recursive uploads from storage Expected results: do recursive uploads Additional info: benefits: * easy to "restore" VMs either from a different storage domain or from your storage domain if you lost DB and your DB backup is too old and does not know about newly created/used VMs it would be also nice if engine-image-uploader could "scan" local storage. example: * multiple VMs on local storage with 'internal layout' but I do not want to upload all of them. and I'm lazy to parse meta files to discover which uuid-based files refers to which VM. it would be nice if engine-image-upload could "scan" this and tell me the names or some other info, so i could upload only specific VM(s) without telling engine-image-upload specific path. thus, make it human friendly :)
I'm closing this as our approach to fixing this is via: RegisterDisk (3.2) and future work on import existing data domain / report orphan disks/vms on existing data domain (for example, bug 716511) *** This bug has been marked as a duplicate of bug 716511 ***