+++ 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
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:
Created attachment 765117 [details] 3.2-sf18 failed new fix
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
Fixed,
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