Red Hat Bugzilla – Bug 1027378
[REPORTS-SETUP] - Unable to drop rhevmreports database using command suggested by installer
Last modified: 2014-01-21 09:56:29 EST
Created attachment 820583 [details]
reports setup log
Description of problem:
Installation found existing rhevmreports database, and suggested solution, which doesn't work.
Welcome to ovirt-engine-reports setup utility
ERROR: Found the database for ovirt-engine-reports, but could not find the WAR directory!
In order to remedy this situation, please drop the ovirt-engine-reports database by executing:
/usr/bin/dropdb -U engine_reports -h localhost -p 5432 rhevmreports
Error encountered while installing ovirt-engine-reports, please consult the log file: /var/log/ovirt-engine/ovirt-engine-reports-setup-2013_11_06_21_47_05.log
# /usr/bin/dropdb -U engine_reports -h localhost -p 5432 rhevmreports
dropdb: could not connect to database postgres: FATAL: Ident authentication failed for user "engine_reports"
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. start rhevm-reports-set
2. stop installation after reports admin user(s) password (deploying server...)
3. start rhevm-reports-set again
setup fails and suggests not working solution
Suggests working solution
# su postgres
bash-4.1$ psql -c 'drop database rhevmreports'
Please submit this patch to ovirt branch as well.
This bug is currently attached to errata RHEA-2013:15115. 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.
verified on is27, rhevm-reports-3.3.0-25.el6ev.noarch
Checking system state... [ ERROR ]
ERROR: Found the database for rhevm-reports, but could not find the WAR directory!
In order to remedy this situation, please drop the rhevmreports database. For example, for local controlled and provisioned setup, one could use the following command:
su postgres -c 'dropdb rhevmreports'
For other cases, please ask your DBA to remove the aforementioned DB.
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.