Bug 977450 - [rhevm-reports_33] - Installation - re-installing reports fails when deleting rhevmreports db
Summary: [rhevm-reports_33] - Installation - re-installing reports fails when deleting...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: ovirt-engine-reports
Version: 3.3.0
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: 3.2.1
Assignee: Yaniv Lavi
QA Contact: David Botzer
URL:
Whiteboard: infra
Depends On: 977360
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-06-24 15:06 UTC by Idith Tal-Kohen
Modified: 2016-02-10 19:29 UTC (History)
10 users (show)

Fixed In Version: rhevm-reports-3.2.1-5.el6ev.noarch.rpm
Doc Type: Bug Fix
Doc Text:
Previously, if the rhevmreports database was dropped, it was not recreated when rhevm-reports was reinstalled. As a result, rhevm-reports-setup failed during the "Exporting adhoc reports" step. The rhevmreports database is now recreated when rhevm-reports is reinstalled.
Clone Of: 977360
Environment:
Last Closed: 2013-07-16 13:28:55 UTC
oVirt Team: Infra
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
3.2-sf18 (316.42 KB, text/plain)
2013-06-25 14:35 UTC, David Botzer
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2013:1074 0 normal SHIPPED_LIVE rhevm-reports 3.2.1 bug fix update 2013-07-16 17:26:25 UTC
Ruby 8671 0 None None None Never
oVirt gerrit 16042 0 None None None Never

Description Idith Tal-Kohen 2013-06-24 15:06:50 UTC
+++ This bug was initially created as a clone of Bug #977360 +++

Description of problem:
rhevm-reports-setup - Installation - re-installing reports fails when deleting rhevmreports db

Version-Release number of selected component (if applicable):
3.3/is2
3.2/sf18.1

How reproducible:
always on both version

Steps to Reproduce:
1.install rhevm+dwh+reports
2.run setup for all
3.verify all db's were created
4.yum remove rhevm-reports
5.dropdb rhevmreports
6.Reinstall rhevm-reports
7.run reports-setup

Actual results:
fails - "Failed while exporting ad hoc reports"

Expected results:
Should recreate the rhevmreports db

Additional info:
Occurs also on 3.2

3.2/sf18.1 /rhevm-reports.noarch 0:3.2.1-4.el6ev

rhevm-reports-setup
Welcome to ovirt-engine-reports setup utility
In order to proceed the installer must stop the ovirt-engine service
Would you like to stop the ovirt-engine service? (yes|no): y
Stopping ovirt-engine...                              [ DONE ]
Please choose a password for the admin users (rhevm-admin and superuser):
Warning: Weak Password.
Re-type password:
Editing XML files...                                  [ DONE ]
Setting DB connectivity...                            [ DONE ]
Exporting adhoc reports...                            [ ERROR ]
Failed while exporting ad hoc reports

Comment 3 David Botzer 2013-06-25 14:03:28 UTC
Got some errors installing:
Resolving Dependencies
--> Running transaction check
---> Package rhevm-reports.noarch 0:3.2.1-5.el6ev will be installed
--> Processing Dependency: rhevm >= 3.2.0 for package: rhevm-reports-3.2.1-5.el6ev.noarch
--> Finished Dependency Resolution
 You could try using --skip-broken to work around the problem
** Found 660 pre-existing rpmdb problem(s), 'yum check' output follows:

Comment 4 David Botzer 2013-06-25 14:35:46 UTC
Created attachment 765117 [details]
3.2-sf18

failed new fix

Comment 5 David Botzer 2013-06-26 05:25:37 UTC
3.2/sf18.1
rhevm-reports-3.2.1-5.el6ev.noarch.rpm
Fix is working when installing clean install

Remove reports pacakge & dropdb, than reinstall & run setup

Comment 6 David Botzer 2013-06-26 11:31:34 UTC
Fixed,

Comment 8 errata-xmlrpc 2013-07-16 13:28:55 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.

http://rhn.redhat.com/errata/RHBA-2013-1074.html


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