Bug 1070735 - [database] do not enable provisioning for remote database [NEEDINFO]
Summary: [database] do not enable provisioning for remote database
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: oVirt
Classification: Retired
Component: ovirt-engine-installer
Version: 3.4
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: 3.4.0
Assignee: Alon Bar-Lev
QA Contact: sefi litmanovich
URL:
Whiteboard: integration
: 1070160 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-02-27 13:14 UTC by Alon Bar-Lev
Modified: 2015-09-09 09:19 UTC (History)
8 users (show)

Fixed In Version: ovirt-3.4.0-rc
Clone Of:
Environment:
Last Closed: 2014-03-31 12:24:52 UTC
oVirt Team: ---
Embargoed:
didi: needinfo?

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 25065 0 None MERGED packaging: setup: database: do not enable provisioning unless actually requested Never
oVirt gerrit 25097 0 None MERGED packaging: setup: database: do not enable provisioning unless actually requested Never

Description Alon Bar-Lev 2014-02-27 13:14:47 UTC 
as-is
Comment 1 Sandro Bonazzola 2014-03-03 14:40:38 UTC 
This BZ should be fixed in oVirt 3.4.0 RC
Comment 2 Alon Bar-Lev 2014-03-04 09:59:01 UTC 
*** Bug 1070160 has been marked as a duplicate of this bug. ***
Comment 3 Jiri Belka 2014-03-19 11:48:33 UTC 
what to test here please? thx!
Comment 4 Alon Bar-Lev 2014-03-19 11:51:36 UTC 
(In reply to Jiri Belka from comment #3)
> what to test here please? thx!

that you can select 'remote' database and you are prompted with credentials input and setup engine is capable of starting with remote database.

Thanks!
Comment 5 Yedidyah Bar David 2014-03-19 12:33:52 UTC 
(In reply to Alon Bar-Lev from comment #4)
> (In reply to Jiri Belka from comment #3)
> > what to test here please? thx!
> 
> that you can select 'remote' database and you are prompted with credentials
> input and setup engine is capable of starting with remote database.
> 
> Thanks!

Also iirc we saw that if you supply remote db credentials with e.g. db name 'engine', and it's not empty, setup tries to create/use 'engine_TIMESTAMP' as is done in provisioning.
Comment 6 sefi litmanovich 2014-03-26 16:44:18 UTC 
Verified on RHEL 6.5, rhevm-3.4.0-0.12.beta2.el6ev.noarch.

setup with remote db was successfull, db is built as expected on remote host and engine is working.
Comment 7 Yedidyah Bar David 2014-03-27 06:40:32 UTC 
(In reply to sefi litmanovich from comment #6)
> Verified on RHEL 6.5, rhevm-3.4.0-0.12.beta2.el6ev.noarch.
> 
> setup with remote db was successfull, db is built as expected on remote host
> and engine is working.

Did you also verify my comment?

Create a remote db, create some table there, then try to use it in setup. What happens?
Comment 8 Sandro Bonazzola 2014-03-31 12:24:52 UTC 
this is an automated message: moving to Closed CURRENT RELEASE since oVirt 3.4.0 has been released
Note You need to log in before you can comment on or make changes to this bug.