Bug 1552533 - change MaxBlockDiskSize to a more clear value as MaxBlockDiskSizeInGigaBytes or MaxBlockDiskSizeInGigiBytes
Summary: change MaxBlockDiskSize to a more clear value as MaxBlockDiskSizeInGigaBytes ...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: BLL.Storage
Version: 4.2.2
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ovirt-4.3.2
: 4.3.2.1
Assignee: Pavel Bar
QA Contact: Avihai
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-03-07 09:51 UTC by Avihai
Modified: 2019-03-19 10:05 UTC (History)
4 users (show)

Fixed In Version: ovirt-engine-4.3.2.1
Doc Type: Bug Fix
Doc Text:
This release renames the 'MaxBlockDiskSize' option to 'MaxBlockDiskSizeInGibiBytes'.
Clone Of:
Environment:
Last Closed: 2019-03-19 10:05:22 UTC
oVirt Team: Storage
Embargoed:
rule-engine: ovirt-4.3+

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 98228 0 master MERGED core: Change config key name 2021-01-17 10:06:56 UTC
oVirt gerrit 98317 0 master MERGED core: rename MaxBlockDiskSize in fn_db_add_config_value 2021-01-17 10:06:57 UTC

Description Avihai 2018-03-07 09:51:58 UTC 
Description of problem:
executing engine config following statement it is not clear in what units MaxBlockDiskSize is ?

> engine-config --get MaxBlockDiskSize
MaxBlockDiskSize: 8192 version: general

Please change MaxBlockDiskSize to either one of the following according to the correct size:

- MaxBlockDiskSizeInGigaBytes(1024B**3)

  or to:

- MaxBlockDiskSizeInGigiBytes(1000B**3) 




Version-Release number of selected component (if applicable):
4.2.2.2-0.1.el7

How reproducible:
100%

Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:
Comment 1 Sandro Bonazzola 2019-01-28 09:34:24 UTC 
This bug has not been marked as blocker for oVirt 4.3.0.
Since we are releasing it tomorrow, January 29th, this bug has been re-targeted to 4.3.1.
Comment 2 Avihai 2019-03-17 13:18:01 UTC 
Verified on ovirt-engine-4.3.2.1-0.1.el7.noarch
Comment 3 Sandro Bonazzola 2019-03-19 10:05:22 UTC 
This bugzilla is included in oVirt 4.3.2 release, published on March 19th 2019.

Since the problem described in this bug report should be
resolved in oVirt 4.3.2 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.
Note You need to log in before you can comment on or make changes to this bug.