Bug 1535904

Summary:	engine-setup creates bad 10-setup-database.conf if it has to provision engine_TIMESTAMP
Product:	[oVirt] ovirt-engine	Reporter:	Yedidyah Bar David <didi>
Component:	Setup.Engine	Assignee:	Yedidyah Bar David <didi>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Jiri Belka <jbelka>
Severity:	urgent	Docs Contact:
Priority:	unspecified
Version:	4.2.0	CC:	bugs, lsvaty
Target Milestone:	ovirt-4.2.1	Keywords:	Regression
Target Release:	4.2.1.2	Flags:	rule-engine: ovirt-4.2+ rule-engine: blocker+
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	https://bugzilla.redhat.com/show_bug.cgi?id=1535904	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:
Clones:	1535935 (view as bug list)		Environment:
Last Closed:	2018-02-12 11:54:28 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	Integration	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Yedidyah Bar David 2018-01-18 08:59:56 UTC

Description of problem:

$summary.

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

Current master. Not sure what changed the order of things so that this didn't happen before.

Comment 1 Yedidyah Bar David 2018-01-18 12:11:30 UTC

86530 is related, but not needed for current bug.

Comment 2 Yedidyah Bar David 2018-01-18 13:44:55 UTC

To reproduce/verify:

Install clean EL7

Install ovirt-engine

/usr/share/ovirt-engine/setup/bin/ovirt-engine-provisiondb --otopi-environment="OVESETUP_PROVISION_DB/database=str:engine OVESETUP_PROVISION_DB/user=str:engine OVESETUP_PROVISION_DB/password=str:secret"

su - postgres -c "scl enable rh-postgresql95 \"psql engine -c 'create table tab1(a int);'\""

engine-setup

Try to connect to the engine

Comment 3 Jiri Belka 2018-01-23 16:48:58 UTC

ok, ovirt-engine-setup-4.2.1.2-0.1.el7.noarch

Comment 4 Sandro Bonazzola 2018-02-12 11:54:28 UTC

This bugzilla is included in oVirt 4.2.1 release, published on Feb 12th 2018.

Since the problem described in this bug report should be
resolved in oVirt 4.2.1 release, it has been closed with a resolution of CURRENT RELEASE.

If the solution does not work for you, please open a new bug report.