Bug 1479752

Summary:	virtual/actual disks size in snapshot is not well formatted
Product:	[oVirt] ovirt-engine	Reporter:	Lucie Leistnerova <lleistne>
Component:	Frontend.WebAdmin	Assignee:	shani <sleviim>
Status:	CLOSED CURRENTRELEASE	QA Contact:	samuel macko <smacko>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	4.2.0	CC:	amureini, bugs, lsvaty
Target Milestone:	ovirt-4.2.0	Keywords:	Regression
Target Release:	---	Flags:	rule-engine: ovirt-4.2+ rule-engine: blocker+
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	No Doc Update
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-12-20 10:43:13 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	Storage	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Lucie Leistnerova 2017-08-09 10:49:52 UTC

Description of problem:
In snapshots subtab Disks are Virtual and Actual size in Bytes. It should be something like 20 GB | < 1 GB

Version-Release number of selected component (if applicable):
ovirt-engine-webadmin-portal-4.2.0-0.0.master.20170808202742.git7c42951.el7.centos.noarch

How reproducible: always


Steps to Reproduce:
1. go to VM detail -> Snapshots
2. expand Disks at Active VM


Actual results:
Virtual Size   10737418240
Actual Size    1286332416


Expected results:
Virtual Size   10 GB
Actual Size    1 GB

Comment 1 Red Hat Bugzilla Rules Engine 2017-08-10 11:52:45 UTC

This bug report has Keywords: Regression or TestBlocker.
Since no regressions or test blockers are allowed between releases, it is also being identified as a blocker for this release. Please resolve ASAP.

Comment 2 samuel macko 2017-09-04 10:33:03 UTC

Verified in ovirt version 4.2.0-0.0.master.20170903205106.gitb17261a.el7.centos.

Verified by following the reproducer.

Comment 3 Sandro Bonazzola 2017-12-20 10:43:13 UTC

This bugzilla is included in oVirt 4.2.0 release, published on Dec 20th 2017.

Since the problem described in this bug report should be
resolved in oVirt 4.2.0 release, published on Dec 20th 2017, it has been closed with a resolution of CURRENT RELEASE.

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