Description of problem:
The wizard that runs when you enter "hosted-engine --deploy" mentions storage sizes in several places. Sometimes the storage unit is GiB, and sometimes it's GB. This inconsistency is confusing and is potentially an unnecessary source of user error.
How reproducible: 100%
Steps to Reproduce:
Run hosted-engine --deploy and notice the different area where units of storage are mentioned.
Here are some examples:
- I was prompted to enter the shared storage disk size in GiB.
- FROM SHE GUIDE: The following luns have been found on the requested target:
 360003ff44dc75adcb5046390a16b4beb 199GiB MSFT Virtual HD
- Please specify the size of the VM disk in GB: :
Consistent terminology, unless there's a clearly called-out reason for the inconsistency.
QE cannot reproduce this bug, test info as blow:
1. Clean install rhvh-18.104.22.168-0.20191024.0
2. Prepare iscsi storage for hosted engine deployment
3. Run hosted-engine --deploy
4. Select iscsi storage type
5. Select the iscsi target and lun
6. Notice the different area where units of storage are mentioned.
Units of storage are consistently displayed.
- The following luns have been found on the requested target:
 36005076300810b3e000000000000029b 80GiB IBM 2145
status: free, paths: 1 active
- Please specify the size of the VM disk in GiB: :
Steve, do you use the iscsi storage for this bug? Or some steps are not correct during the reproducing?
I was using NFS storage. Other than that, your steps for reproducing look fine.
(In reply to Steve Goodman from comment #3)
> I was using NFS storage. Other than that, your steps for reproducing look
Using NFS storage instead, QE still cannot reproduce this bug
-Please specify the size of the VM disk in GiB: :
Change flag to "-"
Test with rhvh-22.214.171.124-0.20191204.0, found a similar issue:
The memory size in VM settings of hosted enging deployment via cockpit. It displays as:
Memory Size(MiB) 16384 62,827MB available
Please refer the attachment picture.
Created attachment 1646023 [details]
Let's handle all those labeling at once in this bug.
We need also to check if it's just labeling or calculations are done on assumptions of using Gib/Mib and getting wrongly inputs in Gb/Mb.
If we have this issue we need to backport this to zstream.
QE will verify this issue until the new build is coming.
Test with RHVH-4.4-20200701.0-RHVH-x86_64-dvd1.iso, cockpit-ovirt-dashboard-0.14.9-1.el8ev.noarch, bug is fixed, move it to "VERIFIED"
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory (RHV RHEL Host (ovirt-host) 4.4), and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.