Bug 993002 - [rhevm_33] - Installation - Cannot install Remote Setup (Based otopi engine setup )
Summary: [rhevm_33] - Installation - Cannot install Remote Setup (Based otopi engine s...
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: ovirt-engine-setup
Version: 3.3.0
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: ---
Assignee: Moran Goldboim
QA Contact: Pavel Stehlik
URL:
Whiteboard: integration
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-08-05 11:43 UTC by David Botzer
Modified: 2014-01-14 00:06 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-08-06 06:40:36 UTC
oVirt Team: ---
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
setuplog (1.36 MB, text/plain)
2013-08-05 11:43 UTC, David Botzer
no flags Details

Description David Botzer 2013-08-05 11:43:24 UTC
Created attachment 782769 [details]
setuplog

Description of problem:
Engine - Installation - Cannot install Remote Setup

Version-Release number of selected component (if applicable):
3.3/is8

How reproducible:
always

Steps to Reproduce:
1.Install two clean RHEL64
2.Install On the first rhevm
3.Install on the second postgres
4.Run engine-setup on the first and select Remote setup

Actual results:
Setup fails, since the engine db password hadn't been generated yet, and there is no other password

Expected results:
Should create engine db on remote server
And Should complete installation successfully

Additional info:
I cant find the engine installation log !!!!

Database password:
[ ERROR ] Cannot connect to database: Cannot connect to database: FATAL:  password authentication failed for user "engine" FATAL:  password authentication failed for user "engine"
============================
/etc/ovirt-engine/engine.conf.d/ --> its empty

Workaround - Install rhevm on remote db server and run engine-setup
After it finishes run engine-cleanup

Comment 1 Itamar Heim 2013-08-06 06:40:36 UTC
I'm missing the part in which you manually created a user on the postgres host for the setup to use.


Note You need to log in before you can comment on or make changes to this bug.