Red Hat Bugzilla – Bug 1006950
Setup - Generated user and password are not saved immediately and are lost upon failure.
Last modified: 2014-01-21 09:59:40 EST
Description of problem: Only at the end of the setup is the created role 'engine_history' user and password saved to config fail. This can block reinstallation due to missing password. Setup should save this right after the creation. Version-Release number of selected component (if applicable): IS14-3.3.0 How reproducible: sometimes Steps to Reproduce: 1. Run setup 2. Fail the setup after role creation, but before config file is created. Actual results: Reinstall doesn't work. Expected results: Should save to file upon creation of role. Additional info:
Verification failed on IS22: rhevm-dwh-3.3.0-20.el6ev.noarch # 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 ] This utility can configure a read only user for DB access. Would you like to do so? (yes|no): y Provide a username for read-only user : ^CError encountered while installing rhevm-dwh, please consult the log file: /var/log/ovirt-engine/rhevm-dwh-setup-2013_11_13_18_25_27.log # rhevm-dwh-setup Welcome to ovirt-engine-dwh setup utility This utility can configure a read only user for DB access. Would you like to do so? (yes|no): yes Provide a username for read-only user : readonly Provide a password for read-only user: Warning: Weak Password. Re-type password: Should postgresql be setup with secure connection? (yes|no): no Creating DB... [ ERROR ] Error encountered while installing rhevm-dwh, please consult the log file: /var/log/ovirt-engine/rhevm-dwh-setup-2013_11_13_18_30_01.log log: 2013-11-13 18:30:29::ERROR::rhevm-dwh-setup::598::root:: Exception caught! 2013-11-13 18:30:29::ERROR::rhevm-dwh-setup::599::root:: Traceback (most recent call last): File "/usr/bin/rhevm-dwh-setup", line 545, in main createDbSchema(db_dict) File "/usr/share/ovirt-engine-dwh/decorators.py", line 28, in wrapped_f raise Exception(instance) Exception: Error while trying to create ovirt_engine_history db database state: psql -l could not change directory to "/root" List of databases Name | Owner | Encoding | Collation | Ctype | Access privileges ----------------------+----------------+----------+-------------+-------------+----------------------- engine | engine | UTF8 | en_US.UTF-8 | en_US.UTF-8 | ovirt_engine_history | engine_history | UTF8 | en_US.UTF-8 | en_US.UTF-8 | postgres | 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 (5 rows)
Created attachment 823460 [details] rhevm-dwh-setup.log
Please attach /var/log/ovirt-engine/rhevm-dwh-setup-2013_11_13_18_30_01.log from the system. The attached bug displays a completely different and unrelated problem.
Created attachment 823824 [details] rhevm-dwh-setup.log Sorry for the wrong log.
Again, wrong log.
(In reply to Alex Lourie from comment #6) > Again, wrong log. comment #5: rhevm-dwh-setup-2013_11_13_18_30_01.log (text/plain), 13.86 KB, created by Barak Dagan on 2013-11-14 04:17 EST. Seems to be what was asked in comment #4 ?
Barak: First log has this: 2013-11-13 18:30:29::DEBUG::rhevm-dwh-setup::151::root:: ovirt engine history db creation is logged at /var/log/ovirt-engine/ovirt-history-db-install-2013_11_13_18_30_29.log Second log has this: 2013-11-13 18:30:29::DEBUG::rhevm-dwh-setup::151::root:: ovirt engine history db creation is logged at /var/log/ovirt-engine/ovirt-history-db-install-2013_11_13_18_30_29.log Which is the same thing. I would like to see the log that ends with 18:30:01, not 18:30:29. Thanks.
Verification passed on IS23, rhevm-dwh-3.3.0-21.el6ev.noarch: # 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 ] This utility can configure a read only user for DB access. Would you like to do so? (yes|no): yes Provide a username for read-only user : rro Provide a password for read-only user: Warning: Weak Password. Re-type password: ^C Error encountered while installing rhevm-dwh, please consult the log file: /var/log/ovirt-engine/rhevm-dwh-setup-2013_11_15_01_00_23.log # rhevm-dwh-setup Welcome to ovirt-engine-dwh setup utility This utility can configure a read only user for DB access. Would you like to do so? (yes|no): yes Provide a username for read-only user : rro Provide a password for read-only user: Warning: Weak Password. Re-type password: Should postgresql be setup with secure connection? (yes|no): no Creating DB... [ DONE ] Creating read-only user...
This bug is currently attached to errata RHEA-2013:15116. 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: https://bugzilla.redhat.com/page.cgi?id=fields.html#cf_release_notes Thanks in advance.
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-0036.html