Bug 1669047

Summary:	Support creating a cinderlib data-base in the engine-setup process
Product:	[oVirt] ovirt-engine	Reporter:	Eyal Shenitzky <eshenitz>
Component:	BLL.Storage	Assignee:	Eyal Shenitzky <eshenitz>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Avihai <aefrat>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	4.3.0	CC:	aefrat, bugs, emarcus, frolland
Target Milestone:	ovirt-4.3.1	Flags:	rule-engine: ovirt-4.3+
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Enhancement
Doc Text:	In order to create and use a Managed block storage domain, a new database must be created that is accessible by cinderlib. In this release, a new database can be created during the engine-setup process, using the same procedures described in the documentation for "Configuring the Red Hat Virtualization Manager".	Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-03-13 16:40:29 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	Storage	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	1539837

Description Eyal Shenitzky 2019-01-24 08:13:30 UTC

Description of problem:

We need to add the option to add the database required by cinderlib in the engine-setup installation process.

Currently, the user should add this DB manually.

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

How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 2 Fred Rolland 2019-01-31 14:06:21 UTC

*** Bug 1664588 has been marked as a duplicate of this bug. ***

Comment 4 Avihai 2019-03-06 08:03:15 UTC

Verified in ovirt-engine Software Version:4.3.1.1-0.1.el7

Comment 6 Sandro Bonazzola 2019-03-13 16:40:29 UTC

This bugzilla is included in oVirt 4.3.1 release, published on February 28th 2019.

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