Created attachment 1405224 [details] Print screens of the issue Description of problem: Via Webadmin try to extend a disk with MaxBlockDiskSize (8192G) with a value of '0' -> wrong error message appears: ' Cannot create disk more than ${max}_disk_size GB' ${max}_disk_size GB should be thee MaxBlockDiskSize value (currently 8192GB), please change it so it will match it. Version-Release number of selected component (if applicable): 4.2.2.2-0.1.el7 How reproducible: 100% Steps to Reproduce: 1. Create a disk(block SD) with MaxBlockDiskSize (8192G) & attach it to a VM1 2. Via VM1 window edit the disk & try to extend it by '0' Actual results: a wrong error message appears (${max}_disk_size should not be there): ' Cannot create disk more than ${max}_disk_size GB' Expected results: the expected error message: 'Cannot create disk more than 8192 GB' Additional info: print screen attahced.
- In Webadmin, inserting a disk size larger than 8192G is blocked with a highlighted disk size field "this field must contain an integer number less than or equal to 0" (the disk size was 8192). - Via REST, the response body for update disk provisioned_size property is: <fault> <detail>[Cannot create disk more than 8192 GB]</detail> <reason>Operation Failed</reason> </fault> The PUT request is: URL = https://engine_addr/ovirt-engine/api/vms/%vm_id%/diskattachments/%disk_id% <disk_attachment> <disk> <provisioned_size>8996093022208</provisioned_size> </disk> </disk_attachment> ===================== Used: ovirt-engine-4.3.0-0.6.alpha2.el7.noarch
This bugzilla is included in oVirt 4.3.0 release, published on February 4th 2019. Since the problem described in this bug report should be resolved in oVirt 4.3.0 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.