Bug 1534913

Summary:	Missing uuid-ossp extension on remote db causes engine-setup to die in the middle
Product:	[oVirt] ovirt-engine	Reporter:	Yedidyah Bar David <didi>
Component:	Setup.Engine	Assignee:	Eli Mesika <emesika>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Lucie Leistnerova <lleistne>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	4.2.0	CC:	bugs, lveyde, mperina
Target Milestone:	ovirt-4.2.2	Flags:	rule-engine: ovirt-4.2+
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	ovirt-engine-4.2.2	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-03-29 11:14:23 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	Infra	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	1515635
Bug Blocks:

Description Yedidyah Bar David 2018-01-16 09:39:57 UTC

Description of problem:

See comment in:

https://gerrit.ovirt.org/#/c/84832/25/packaging/setup/plugins/ovirt-engine-setup/ovirt-engine/db/configuration.py@308

engine-setup should check existence of the extension at an earlier stage, probably STAGE_VALIDATION, and perhaps also prompt the user to fix this instead of aborting.

Aborting in the middle of the transaction should be avoided as much as possible.

Comment 1 Martin Perina 2018-01-16 10:00:43 UTC

Let's improve it and add that extension check earlier in engine-setup in 4.2.2 release

Comment 2 Yedidyah Bar David 2018-01-16 12:33:34 UTC

See also documentation bug 1534928 for what to actually do with a remote database.

Comment 3 Lucie Leistnerova 2018-02-21 15:39:03 UTC

check for uuid-ossp is done in Stage: Setup validation, so before any action is done

verified in ovirt-engine-setup-4.2.2-0.1.el7.noarch

Comment 4 Sandro Bonazzola 2018-03-29 11:14:23 UTC

This bugzilla is included in oVirt 4.2.2 release, published on March 28th 2018.

Since the problem described in this bug report should be
resolved in oVirt 4.2.2 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.