Description of problem: Same as BZ1054259 but for rhevm-reports-setup... [root@test ~]# rhevm-reports-setup Welcome to rhevm-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): Would you like to stop the ovirt-engine service (yes|no): yes Stopping ovirt-engine... [ DONE ] Remote database not found. 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 rhevmreports template template0 encoding 'UTF8' lc_collate 'en_US.UTF-8' lc_ctype 'en_US.UTF-8' owner <role>; Provide a remote DB user : remote_rhevmreports Please choose a password for the db user: Re-type password: Editing XML files... [ DONE ] Setting DB connectivity... [ DONE ] Please choose a password for the reports admin user(s) (rhevm-admin and superuser): Warning: Weak Password. Retype password: Warning: Weak Password. Deploying Server... Version-Release number of selected component (if applicable): is32.2 - rhevm-reports-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 remote_rhevmreports template template0 encoding 'UTF8' lc_collate 'en_US.UTF-8' lc_ctype 'en_US.UTF-8' owner <role>;" 3. rhevm-reports-setup and try to user 'remote_rhevmrepors' DB Actual results: rhevm-reports-setup has hardcoded DB name Expected results: ask user for DB name (as he created the DB called 'remote_rhevmreports') Additional info:
This bug affects only 3.3. In 3.4+ we do ask for everything. Not sure we should really solve it for 3.3 at this point in time.
should be in the code of first release. Please test once it's out. Yaniv
Hi didi, I have updated the doc text. Please let me know if this is correct or not. Cheers, Julie
Looks good to me.
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. https://rhn.redhat.com/errata/RHEA-2015-0176.html