Bug 1459134

Summary:	[RFE] Rebase engine-setup on PostgreSQL >= 9.5
Product:	[oVirt] ovirt-engine	Reporter:	Sandro Bonazzola <sbonazzo>
Component:	Setup.Engine	Assignee:	Yedidyah Bar David <didi>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Lucie Leistnerova <lleistne>
Severity:	high	Docs Contact:
Priority:	urgent
Version:	4.2.0	CC:	bugs, lsvaty, mperina, stirabos, trichard, ylavi
Target Milestone:	ovirt-4.2.0	Keywords:	FutureFeature, Rebase
Target Release:	4.2.0	Flags:	rule-engine: ovirt-4.2+ lleistne: testing_plan_complete- ylavi: planning_ack+ sbonazzo: devel_ack+ lsvaty: testing_ack+
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Enhancement
Doc Text:	With this release, the engine now requires PostgreSQL 9.5 or later, which provides new features and better performance. The engine-setup tool can help upgrade an existing database to Software Collections PostgreSQL 9.5, as well as use that version for new setups.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-12-20 11:41:04 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:
Bug Depends On:	1480624, 1488189, 1490936
Bug Blocks:	1106547, 1470985, 1470988, 1470991, 1470992, 1470994

Description Sandro Bonazzola 2017-06-06 12:00:42 UTC

In Fedora >= 24 we already have PostgreSQL >= 9.5.
In CentOS / RHEL PostgreSQL is available using software collections.
We should be able to upgrade from 4.1 to 4.2 enabling PostgreSQL >= 9.5 as part of the update.

Comment 1 Lucie Leistnerova 2017-08-24 14:03:45 UTC

This scenarios should be tested:

1. fresh install 4.2, postgres 9.5
2. upgrade 4.1, postgres < 9.5 => 4.2, postgres 9.5
3. upgrade 4.2, postgres 9.5 => newer 4.2, postgres 9.5
4. fresh install 4.2, postgres 9.6
5. upgrade 4.1, postgres < 9.5 => 4.2, postgres 9.6
6. upgrade 4.2, postgres 9.5 => newer 4.2, postgres 9.6

Notice: 4.2 will work only with postgres >= 9.5 and so can't be installed with lower postgres versions.

Comment 2 Simone Tiraboschi 2017-09-05 08:29:48 UTC

(In reply to Lucie Leistnerova from comment #1)
> This scenarios should be tested:

We need also to consider that we have the engine, engine DB, DWH and DWH DB and all of them could be on the same machine or on 4 distinct machines in the worst case.

Comment 3 Lucie Leistnerova 2017-11-02 10:16:11 UTC

Scenarios from Comment 1 were tested for:

- dwh, engine both service and db locally
- dwh, engine service locally, dwh, engine's db remotely
- engine both service and db locally, dwh both service and db remotely

Some errors occurred, see depending BZ. It all should be fixed now, so engine is working well with postgres 9.5 and 9.6 in main functions.

Comment 4 Sandro Bonazzola 2017-12-20 11:41:04 UTC

This bugzilla is included in oVirt 4.2.0 release, published on Dec 20th 2017.

Since the problem described in this bug report should be
resolved in oVirt 4.2.0 release, published on Dec 20th 2017, it has been closed with a resolution of CURRENT RELEASE.

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