Bug 1067548
| Summary: | [DWH-SETUP][TEXT] - misconfiguartion of remote DB setup | ||
|---|---|---|---|
| Product: | [Retired] oVirt | Reporter: | Barak Dagan <bdagan> |
| Component: | ovirt-engine-installer | Assignee: | Alon Bar-Lev <alonbl> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Barak Dagan <bdagan> |
| Severity: | low | Docs Contact: | |
| Priority: | medium | ||
| Version: | 3.4 | CC: | acathrow, alonbl, bazulay, dariusz.kryszak, didi, gklein, iheim, knesenko, pstehlik, sbonazzo, yeylon, ylavi |
| Target Milestone: | --- | ||
| Target Release: | 3.4.0 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | integration | ||
| Fixed In Version: | ovirt-engine-3.4.0_rc | Doc Type: | Bug Fix |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2014-03-31 12:31:47 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | |||
| Bug Blocks: | 1024889 | ||
Setting target release to current version for consideration and review. please do not push non-RFE bugs to an undefined target release to make sure bugs are reviewed for relevancy, fix, closure, etc. This is an automated message. Re-targeting all non-blocker bugs still open on 3.4.0 to 3.4.1. Maybe this is worth to be fixed in 3.4.0. It seems a low risk one and avoid headache trying to figure out why remote db connection fails... Why there is no log attached? Why trivial issues are not handled at same day issue is found? Moving to core product to fix all satellite packages. verification failed on av3: create ovirt_engine_history engine owner ovirt_engine_history <= ????? template template0 encoding 'UTF8' lc_collate 'en_US.UTF-8' lc_ctype 'en_US.UTF-8'; (In reply to Barak Dagan from comment #6) > verification failed on av3: > > create ovirt_engine_history engine owner ovirt_engine_history <= ????? > template template0 > encoding 'UTF8' lc_collate 'en_US.UTF-8' > lc_ctype 'en_US.UTF-8'; Nice!!! :) /me cannot read. looks like all patches have been merged, anything else left? (In reply to Sandro Bonazzola from comment #8) > looks like all patches have been merged, anything else left? I truly hope so. this is an automated message: moving to Closed CURRENT RELEASE since oVirt 3.4.0 has been released Finally, everything works fine. Full reinstallation DWH and Reports engine has resolved problem. Problem has been occured because description from the ovirt website (http://www.ovirt.org/Ovirt_Reports) is not consequent. As I understand installation procedure for 3.5 version doesn't require additional installation of the DWH package. I was wrong. It is. |
Description of problem: During installation, there are instruction for manual action over the remote server: Please create database for ovirt-engine-dwh use. Use the following commands as an example: create role engine_history with login encrypted password 'engine_history';create database engine_history owner engine_history template template0 encoding 'UTF8' lc_collate 'en_US.UTF-8' lc_ctype 'en_US.UTF-8'; During the setup, the defaults are different: DWH database host [localhost]: my.remote.server.redhat.com DWH database port [5432]: DWH database secured connection (Yes, No) [No]: DWH database name [ovirt_engine_history]: DWH database user [ovirt_engine_history]: engine_history DWH database password: [ ERROR ] Cannot connect to DWH database: Cannot connect to database: FATAL: database "ovirt_engine_history" does not exist Version-Release number of selected component (if applicable): ovirt-engine-3.4.0-0.11.beta3.el6.noarch ovirt-engine-dwh-setup-3.4.0-0.3.el6.noarch How reproducible: 100% Steps to Reproduce: 1. install dwh over remote db server 2. 3. Actual results: 1) The instructions are not indented correctly 2) In the instruction the role, db & passwrod are engine_history 3) The defult answer for role & db are ovirt_engine_history 4) In previous version the role & password were selected by the user. If this is the case here, please fix the instruction, if the names are fixed, why asking for them ? Expected results: Additional info: