Bug 1578144 - hosted-engine deploy asks for VM size using wrong units
Summary: hosted-engine deploy asks for VM size using wrong units
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: ovirt-hosted-engine-setup
Classification: oVirt
Component: UX
Version: 2.2.19
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ovirt-4.2.5
: 2.2.23
Assignee: Asaf Rachmani
QA Contact: Shir Fishbain
URL:
Whiteboard:
Depends On:
Blocks: ovirt-hosted-engine-setup-2.2.24
TreeView+ depends on / blocked
 
Reported: 2018-05-14 21:34 UTC by Robert Story
Modified: 2018-07-31 15:28 UTC (History)
3 users (show)

Fixed In Version: ovirt-hosted-engine-setup-2.2.23-1.el7ev
Clone Of:
Environment:
Last Closed: 2018-07-31 15:28:02 UTC
oVirt Team: Integration
Embargoed:
rule-engine: ovirt-4.2+


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 92326 0 master MERGED src: plugins: Ask user to specify VM disk in GiB 2021-02-17 13:11:25 UTC
oVirt gerrit 92390 0 ovirt-hosted-engine-setup-2.2 MERGED src: plugins: Ask user to specify VM disk in GiB 2021-02-17 13:11:25 UTC

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.


Note You need to log in before you can comment on or make changes to this bug.