Bug 1039459 - [REPORTS-SETUP] - reports installation (upgrade) failed from 3.1.5.1 -> 3.2.5 -> 3.3 (is26)
Summary: [REPORTS-SETUP] - reports installation (upgrade) failed from 3.1.5.1 -> 3.2.5...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: ovirt-engine-reports
Version: unspecified
Hardware: Unspecified
OS: Unspecified
unspecified
urgent
Target Milestone: ---
: 3.3.0
Assignee: Yaniv Lavi
QA Contact: Barak Dagan
URL:
Whiteboard: integration
Depends On:
Blocks: 1043314 3.3rc1
TreeView+ depends on / blocked
 
Reported: 2013-12-09 07:21 UTC by Barak Dagan
Modified: 2015-09-22 13:10 UTC (History)
6 users (show)

Fixed In Version: is27
Doc Type: Bug Fix
Doc Text:
Upgrading the rhevm-reports from version 3.1 failed with the error "database "ovirtenginereports" does not exist" because the database name had been changed to rhevmreports. This has now been fixed, so installing rhevm-reports succeeds.
Clone Of:
Environment:
Last Closed: 2014-01-21 14:56:35 UTC
oVirt Team: ---
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
failed log (16.32 KB, text/plain)
2013-12-09 07:21 UTC, Barak Dagan
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2014:0035 0 normal SHIPPED_LIVE rhevm-reports 3.3 bug fix and enhancement update 2014-01-21 19:53:30 UTC

Description Barak Dagan 2013-12-09 07:21:49 UTC
Created attachment 834223 [details]
failed log

Description of problem:

on clean enviourment, si29.4 was installed, setup was set (5 running vms) + dwh & reports.
That engine was upgraded to latests 3.2 (sf22), and then to 3.3.
reports upgrade failed due to db name change.

--- console ---
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): yes
Stopping ovirt-engine...                              [ DONE ]
Return Code is not zero
Error encountered while installing ovirt-engine-reports, please consult the log file: /var/log/ovirt-engine/ovirt-engine-reports-setup-2013_12_08_21_36_22.log

--- log ---
2013-12-08 21:54:22:EBUG::common_utils::1028::root:: stderr = psql: FATAL:  database "ovirtenginereports" does not exist

--- postgres ---
# su - postgres -c "psql -l"
                                       List of databases
         Name         |  Owner   | Encoding |  Collation  |    Ctype    |   Access privileges  
----------------------+----------+----------+-------------+-------------+-----------------------
 engine               | engine   | UTF8     | en_US.UTF-8 | en_US.UTF-8 |
 ovirt_engine_history | postgres | UTF8     | en_US.UTF-8 | en_US.UTF-8 |
 postgres             | postgres | UTF8     | en_US.UTF-8 | en_US.UTF-8 |
 rhevmreports         | postgres | UTF8     | en_US.UTF-8 | en_US.UTF-8 |
 template0            | postgres | UTF8     | en_US.UTF-8 | en_US.UTF-8 | =c/postgres
                                                                        : postgres=CTc/postgres
 template1            | postgres | UTF8     | en_US.UTF-8 | en_US.UTF-8 | =c/postgres
                                                                        : postgres=CTc/postgres



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

How reproducible:
1 out 1 attempts

Steps to Reproduce:
1. mentioned in the description
2.
3.

Actual results:
report-setup failed on is26

Expected results:
sucessfull installation

Additional info:

Comment 1 Barak Dagan 2013-12-18 10:48:37 UTC
verified on IS27:

# rhevm-reports-setup -a 33.local.reports.ansfile 
Welcome to rhevm-reports setup utility
Stopping ovirt-engine...                              [ DONE ]
Editing XML files...                                  [ DONE ]
Setting DB connectivity...                            [ DONE ]

(however the upgarde failed due to https://bugzilla.redhat.com/show_bug.cgi?id=1043314)

Comment 3 errata-xmlrpc 2014-01-21 14:56:35 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-2014-0035.html


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