Bug 1390498
| Summary: | [v4 REST-API] Read only Attribute is missing from /api/disks/{disk id}/ or from /api/vms/{vm id}/diskattachments/{diskattachments id} | ||
|---|---|---|---|
| Product: | [oVirt] ovirt-engine | Reporter: | Eyal Shenitzky <eshenitz> |
| Component: | RestAPI | Assignee: | Tal Nisan <tnisan> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Lilach Zitnitski <lzitnits> |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | 4.0.5.1 | CC: | amureini, bugs, eshenitz, lveyde, ratamir, tnisan, ylavi |
| Target Milestone: | ovirt-4.1.2 | Keywords: | Automation, AutomationBlocker |
| Target Release: | 4.1.2 | Flags: | rule-engine:
ovirt-4.1+
ylavi: blocker+ |
| 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: | 2017-05-23 08:14:18 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: | |||
The RO attribute was never moved to diskattachments, although logically it definitely belongs there. Targeting for 4.1. This blocks all our 4.1 read only disks testing - changed the severity to high This bug report has Keywords: Regression or TestBlocker. Since no regressions or test blockers are allowed between releases, it is also being identified as a blocker for this release. Please resolve ASAP. (In reply to Raz Tamir from comment #2) > This blocks all our 4.1 read only disks testing - changed the severity to > high Does it work with v3 API? In V3 there is no diskattachment object, the read only attribute was under /api/disks/{disk id}/
This bug report has Keywords: Regression or TestBlocker. Since no regressions or test blockers are allowed between releases, it is also being identified as a blocker for this release. Please resolve ASAP. Moving out all non blocker\exceptions. Tal, do we need to document anything here, or is the API self-documenting? All relevant documentation is in the API --------------------------------------
Tested with the following code:
----------------------------------------
rhevm-4.1.2-0.1.el7.noarch
vdsm-4.19.11-1.el7ev.x86_64
Tested with the following scenario:
Steps to Reproduce:
1. Create a VM with read-only disk attached
2. Check /api/vms/{vm id}/diskattachments/{diskattachments id}
Actual results:
Read_only attribute is found under /api/vms/{vm id}/diskattachments/{disk id}
Expected results:
Moving to VERIFIED!
|
Description of problem: Read only Attribute is missing from /api/disks/{disk id}/ or from /api/vms/{vm id}/diskattachments/{diskattachments id} Version-Release number of selected component (if applicable): Engine - 4.0.5.1-0.1.el7ev How reproducible: 100% Steps to Reproduce: 1. Create a VM with read-only disk attached 2. Check /api/disks/{disk id}/ 3. Check /api/vms/{vm id}/diskattachments/{diskattachments id} Actual results: Read-only Attribute is missing Expected results: Read-only attribute should found under /api/disks/{disk id}/ Additional info: