Bug 1270448

Summary: Calculate storage free space incorrectly during rhevh TUI installation.
Product: Red Hat Enterprise Virtualization Manager Reporter: Ying Cui <ycui>
Component: ovirt-nodeAssignee: Ryan Barry <rbarry>
Status: CLOSED ERRATA QA Contact: Ying Cui <ycui>
Severity: medium Docs Contact:
Priority: medium    
Version: 3.6.0CC: amureini, cshao, dfediuck, fdeutsch, gklein, lsurette, ycui, ykaul
Target Milestone: ovirt-3.6.1   
Target Release: 3.6.1   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: ovirt-node-3.6.0-0.22.20151126git72acbb2.el7 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-03-09 14:40:29 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Node RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
pic_incorrect_free_space none

Description Ying Cui 2015-10-10 07:23:42 UTC
Description of problem:
Here calculate storage free space size is data size when "Fill disk with Data partition" is selected as default in installer TUI.

Version-Release number of selected component (if applicable):
rhev-hypervisor7-7.2-201509280
ovirt-node-3.3.0-0.10.20150928gite7ee3f1.el7ev.noarch 

How reproducible:
100%

Steps to Reproduce:
1.TUI clean install RHEV-H7-7.2-20150928
2.One by one step to storage volume page
3.The "Fill disk with Data partition" is selected as default.
4.Click on "Continue"
5.In confirmation disk page, check "Free Space" and "Data Size"

Actual results:
Free space is the same as Data Size, that is incorrect.

Expected results:
In this case, Free space should be 0 MB, not the same as Data Size.

Comment 1 Ying Cui 2015-10-10 07:24:24 UTC
Created attachment 1081530 [details]
pic_incorrect_free_space

Comment 2 Ying Cui 2015-10-10 07:26:31 UTC
No useful log for this action, so please check the attachment pic to get more.

Comment 9 errata-xmlrpc 2016-03-09 14:40:29 UTC
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, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHBA-2016-0378.html