Description of problem:

# rhevm-dwh-setup 
Welcome to ovirt-engine-dwh 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 ]
Remote installation is selected.

Remote installation selected. Make sure that DBA creates a user and the database in the following fashion:
        create role <role> with login encrypted password <password>;
        create database ovirt_engine_history template template0 encoding 'UTF8' lc_collate 'en_US.UTF-8' lc_ctype 'en_US.UTF-8' owner <role>;

Provide a remote DB user:  :  [engine_history]remote_engine_history
Please choose a password for the db user: 
Warning: Weak Password.
Re-type password: 
Could not connect to remote database - please try again.

^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ - yes, my DB was not called 'ovirt_engine_history' but 'remote_engine_history' as it was hosted on other RHEVM setup (but not having dwh/reports configured).


I found in PG log that there was an attempt to connect to 'ovirt_engine_history'.

# egrep "^(FATAL|ERROR)" /var/lib/pgsql/data/pg_log/postgresql-Thu.log
ERROR:  syntax error at or near "ls" at character 1
FATAL:  password authentication failed for user "engine_history"
FATAL:  database "ovirt_engine_history" does not exist
FATAL:  password authentication failed for user "engine_history"
FATAL:  database "ovirt_engine_history" does not exist
FATAL:  Ident authentication failed for user "root"
FATAL:  Ident authentication failed for user "postgres"
ERROR:  relation "history_configuration" does not exist at character 15
ERROR:  relation "history_configuration" does not exist at character 15
ERROR:  relation "history_configuration" does not exist at character 15


`rhevm-dwh-setup' should allow to define DB name for (remote) installations.

Version-Release number of selected component (if applicable):
is32.2 - rhevm-dwh-3.3.0-28.el6ev.noarch

How reproducible:
100%

Steps to Reproduce:
1. clean remote install for engine
2. remote DB host: "create role <role> with login encrypted password <password>;" + "create database foobar template template0 encoding 'UTF8' lc_collate 'en_US.UTF-8' lc_ctype 'en_US.UTF-8' owner <role>;"
3. rhevm-dwh-setup

Actual results:
rhevm-dwh-setup has hardcoded DB name

Expected results:
ask user for DB name (as he created the DB called 'foobar')

Additional info: