Bug 1578144

Summary: hosted-engine deploy asks for VM size using wrong units
Product: [oVirt] ovirt-hosted-engine-setup Reporter: Robert Story <rs>
Component: UXAssignee: Asaf Rachmani <arachman>
Status: CLOSED CURRENTRELEASE QA Contact: Shir Fishbain <sfishbai>
Severity: medium Docs Contact:
Priority: medium    
Version: 2.2.19CC: bugs, dfediuck, stirabos
Target Milestone: ovirt-4.2.5Keywords: EasyFix
Target Release: 2.2.23Flags: rule-engine: ovirt-4.2+
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: ovirt-hosted-engine-setup-2.2.23-1.el7ev Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-07-31 15:28:02 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Integration RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1596330    

Description Robert Story 2018-05-14 21:34:50 UTC
Description of problem:
hosted-enging deploy asks for VM size in "GB", but creates LV in GiB.

Version-Release number of selected component (if applicable):
ovirt-hosted-engine-setup-2.2.20-1.el7.centos.noarch

How reproducible:
always

Steps to Reproduce:
1. run hoste-engine --deploy
2. enter "GB" value
3. after completing, lvscan will show LV with sin in GiB

Actual results:
script asks for units in GB

Expected results:
script asks for units in GiB

Additional info:

[ INFO  ] iSCSI connected paths: 1
          Please specify the size of the VM disk in GB: [50]: 58

  ACTIVE            '/dev/9c..99' [58.00 GiB] inherit

58 GB is 54.02 GiB

Comment 1 Shir Fishbain 2018-07-09 14:58:36 UTC
The GB changed to GiB when we're asked on "Please specify the size of the VM disk in GB: [50]: 58".

4.2.5.1_SNAPSHOT-73.g63529de.0.scratch.master.el7ev

Comment 2 Sandro Bonazzola 2018-07-31 15:28:02 UTC
This bugzilla is included in oVirt 4.2.5 release, published on July 30th 2018.

Since the problem described in this bug report should be
resolved in oVirt 4.2.5 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.