Bug 1147860
| Summary: | [Tracker] Exporting, moving and copying LUN disks and VM's LUN disks fail in the REST API | ||
|---|---|---|---|
| Product: | [oVirt] ovirt-engine | Reporter: | Idan Shaby <ishaby> |
| Component: | RestAPI | Assignee: | Vered Volansky <vered> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Carlos Mestre González <cmestreg> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | --- | CC: | amureini, bugs, ecohen, gklein, juan.hernandez, lsurette, rbalakri, yeylon, ylavi |
| Target Milestone: | ovirt-3.6.0-rc | Keywords: | Tracking |
| Target Release: | 3.6.0 | Flags: | rule-engine:
ovirt-3.6.0+
ylavi: planning_ack+ rule-engine: devel_ack+ rule-engine: testing_ack+ |
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | storage | ||
| Fixed In Version: | 3.6.0-12 | Doc Type: | Bug Fix |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2015-11-04 11:26:02 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | Storage | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | 1126425, 1147861, 1147863, 1147870, 1147873, 1147874, 1288366 | ||
| Bug Blocks: | |||
|
Description
Idan Shaby
2014-09-30 08:36:05 UTC
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. |