Bug 1560208
Summary: | Resize disk: IO exception while processing "PUT" request for path /vms/%vm_id%/diskattachments/%disk_id% with a number too large for the size | ||||||||
---|---|---|---|---|---|---|---|---|---|
Product: | [oVirt] ovirt-engine | Reporter: | Elad <ebenahar> | ||||||
Component: | BLL.Storage | Assignee: | Allon Mureinik <amureini> | ||||||
Status: | CLOSED CURRENTRELEASE | QA Contact: | Yosi Ben Shimon <ybenshim> | ||||||
Severity: | low | Docs Contact: | |||||||
Priority: | unspecified | ||||||||
Version: | 4.2.2 | CC: | bugs, mperina, oliel, omachace, tnisan | ||||||
Target Milestone: | ovirt-4.2.3 | Keywords: | Automation | ||||||
Target Release: | --- | Flags: | rule-engine:
ovirt-4.2+
|
||||||
Hardware: | x86_64 | ||||||||
OS: | Unspecified | ||||||||
Whiteboard: | |||||||||
Fixed In Version: | Doc Type: | If docs needed, set a value | |||||||
Doc Text: | Story Points: | --- | |||||||
Clone Of: | Environment: | ||||||||
Last Closed: | 2018-05-10 06:31:16 UTC | Type: | Bug | ||||||
Regression: | --- | Mount Type: | --- | ||||||
Documentation: | --- | CRM: | |||||||
Verified Versions: | Category: | --- | |||||||
oVirt Team: | Infra | RHEL 7.3 requirements from Atomic Host: | |||||||
Cloudforms Team: | --- | Target Upstream Version: | |||||||
Embargoed: | |||||||||
Attachments: |
|
Description
Elad
2018-03-24 21:49:22 UTC
Created attachment 1412609 [details]
engine.log and server.log
Seems like it's a general scenario while inputting big numbers and their validation via the REST infrastructure, moving to infra for inspection (In reply to Tal Nisan from comment #2) > Seems like it's a general scenario while inputting big numbers and their > validation via the REST infrastructure, moving to infra for inspection Indeed. The same behavior is observed when trying to update a VM's memory, e.g.: PUT http://mureinik.localdomain:8080/ovirt-engine/api/vms/145d1e47-7a4c-4668-b70a-796378a7b947 BODY: <vm> <memory>171785304187493941248</memory> </vm> It seems to me that both VM memory and Disk size are defined as integers and not longs, that's why those errors are raise. Parsing HTPP content and storing those into model classes is performed in the RestEasy, Ondro/Ori is there any way how to return more descriptive error there Tested using: ovirt-engine-4.2.3.2-0.1.el7.noarch Two requests via REST-API: 1) - url: https://storage-ge-17.scl.lab.tlv.redhat.com/ovirt-engine/api/vms/3cb0d402-e5aa-4cb8-b9c9-b9cc8262fffb - body: <vm> <memory>171785304187493941248</memory> </vm> - response: <fault> <detail>Value 171785304187493941248 is greater than maximum long 9223372036854775807</detail> <reason>Invalid value</reason> </fault> 2) - url: https://storage-ge-17.scl.lab.tlv.redhat.com/ovirt-engine/api/vms/3cb0d402-e5aa-4cb8-b9c9-b9cc8262fffb/diskattachments/536ea3d0-45f3-4679-8c9f-584bfbee186d - body: <disk_attachment> <disk> <alias>test_VM_Disk1</alias> <provisioned_size>171785304187493941248</provisioned_size> </disk> </disk_attachment> - response: <fault> <detail>Value 171785304187493941248 is greater than maximum long 9223372036854775807</detail> <reason>Invalid value</reason> </fault> ========== No exceptions from engine side. Moving to VERIFIED This bugzilla is included in oVirt 4.2.3 release, published on May 4th 2018. Since the problem described in this bug report should be resolved in oVirt 4.2.3 release, it has been closed with a resolution of CURRENT RELEASE. If the solution does not work for you, please open a new bug report. |