Red Hat Bugzilla – Bug 1019758
[DWH] installation - misleading message
Last modified: 2014-07-13 19:19:44 EDT
Description of problem:
Please rephrase these sentences:
...The detected DB size is 51993 Mb. This process can take a considerable time, and in some cases may take few hours to complete...
From above one can feel, that after analyse (Detected DB size - 50MB) this specific amount of data could take like an hour. If installer is not analysing anything, maybe better formulate sentences similar to:
"... The detected DB size is 52 MB. In some specific cases backup may take few hours to complete..."
This process of backup for 50MB took 2s.
Of course more precise estimation would be nice, however I think for such significant change is a bit late.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. install rhevm-dwh, rhevm-reports
2. run rhevm-dwh-setup again
Arthur please consult on the message format.
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?
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.
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.