Description of problem: When trying to export/move a VM LUN disk, and when trying to export/move/copy a LUN disk in the REST API, a "500 Internal Server Error" is returned. Version-Release number of selected component (if applicable): 4792bd921cd73b01a990065607561c4ad2b2c486 How reproducible: 100% Steps to Reproduce: 1. Create a VM. 2. Add an external disk to the VM. 3. From the REST API, run a POST request with one of the operations - export/move/copy. Actual results: A "500 Internal Server Error" is returned. Expected results: An informative error message should be returned, or maybe we should even remove these options for LUN disks in the REST API. Additional info:
Do we still plan to fix this for 3.6.0? As it isn't really of high severity I'd suggest to move it to 4.0.
(In reply to Juan Hernández from comment #1) > Do we still plan to fix this for 3.6.0? As it isn't really of high severity > I'd suggest to move it to 4.0. I guess this is basically a capacity issue. I'd prefer leaving this in 3.6.0 and pushing them out only when we we're nearing the finish line.
Marking this as tested, verified on move/export/copy for lun disks and move/export for vm disk, message is the same except for the specific $action (move, copy, export): <fault> <reason>Operation Failed</reason> <detail> [Cannot $action Virtual Machine Disk. Action is unsupported for the specified disk type (LUN).] </detail> 3.6.0-13 One minor issue is when calling the api for the disk (not vm disk) the message is the same, "Virtual Machine Disk", when that's not the case. I think the message should be fixed accordingly if it's a VM disk or just a 'regular disk'. Allon/Yaniv what do you think?
The term Virtual Machine Disk is used throughout the engine CDA messages, not only for these newly added messages. It's a trivial patch to change it, but I'm not sure that would be the right thing to do. Leaving to Yaniv to decide.
(In reply to Allon Mureinik from comment #4) > The term Virtual Machine Disk is used throughout the engine CDA messages, > not only for these newly added messages. > > It's a trivial patch to change it, but I'm not sure that would be the right > thing to do. > Leaving to Yaniv to decide. I think 'Virtual Disk' or 'vDisk' should be used to describe the VM's disks. But we should open a new request for this since this is not a critical to fix in 3.6.
(In reply to Yaniv Dary from comment #5) > (In reply to Allon Mureinik from comment #4) > > The term Virtual Machine Disk is used throughout the engine CDA messages, > > not only for these newly added messages. > > > > It's a trivial patch to change it, but I'm not sure that would be the right > > thing to do. > > Leaving to Yaniv to decide. > > I think 'Virtual Disk' or 'vDisk' should be used to describe the VM's disks. > But we should open a new request for this since this is not a critical to > fix in 3.6. Agreed. I opened bug 1271698 to track this for the next release, and am marking this one as VERIFIED based on comment 3.
oVirt 3.6.0 has been released on November 4th, 2015 and should fix this issue. If problems still persist, please open a new BZ and reference this one.