Bug 1019741 - [DWH] installation - size of the detected DB should be in MB
[DWH] installation - size of the detected DB should be in MB
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: ovirt-engine-dwh (Show other bugs)
Unspecified Unspecified
unspecified Severity high
: ---
: 3.3.0
Assigned To: Sandro Bonazzola
Barak Dagan
: EasyFix, Triaged
Depends On:
  Show dependency treegraph
Reported: 2013-10-16 06:42 EDT by Pavel Stehlik
Modified: 2014-07-13 19:19 EDT (History)
8 users (show)

See Also:
Fixed In Version: rhevm-reports-3.3.0-13.el6ev.noarch.rpm
Doc Type: Bug Fix
Doc Text:
The database size is now reported in human-readable format, using megabytes or gigabytes.
Story Points: ---
Clone Of:
Last Closed: 2014-01-21 10:00:54 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

External Trackers
Tracker ID Priority Status Summary Last Updated
oVirt gerrit 20261 None None None Never

  None (edit)
Description Pavel Stehlik 2013-10-16 06:42:34 EDT
Description of problem:
 Currently we're telling size in Mb, we should use more reasonable units (MB/GB?).

Existing DB was found on the system. The size of the detected DB is 51993 Mb, free space in the backup folder /var/lib/ovirt-engine/backups is 16132075 Mb.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. install rhevm-dwh
2. after success try to run rhevm-dwh-setup again

Actual results:
displayed units are Mb

Expected results:
display MB/GB

Additional info:
Comment 3 Barak Dagan 2013-10-31 13:15:38 EDT
Verified on IS21:

The upgrade utility can backup the existing database. The time and space required for the database backup depend on its size. The detected DB size is 25 MB. This process takes time, and in some cases (for instance, when the size is few GBs) may take few hours to complete. Would you like to continue and backup the existing database?
Comment 4 Charlie 2013-11-27 19:53:37 EST
This bug is currently attached to errata RHEA-2013:15116. If this change is not to be documented in the text for this errata please either remove it from the errata, set the requires_doc_text flag to 
minus (-), or leave a "Doc Text" value of "--no tech note required" if you do not have permission to alter the flag.

Otherwise to aid in the development of relevant and accurate release documentation, please fill out the "Doc Text" field above with these four (4) pieces of information:

* Cause: What actions or circumstances cause this bug to present.
* Consequence: What happens when the bug presents.
* Fix: What was done to fix the bug.
* Result: What now happens when the actions or circumstances above occur. (NB: this is not the same as 'the bug doesn't present anymore')

Once filled out, please set the "Doc Type" field to the appropriate value for the type of change made and submit your edits to the bug.

For further details on the Cause, Consequence, Fix, Result format please refer to:


Thanks in advance.
Comment 7 errata-xmlrpc 2014-01-21 10:00:54 EST
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.


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