Bug 1431811

Summary:	CloudForms database not properly setup
Product:	Red Hat Quickstart Cloud Installer	Reporter:	Thom Carlin <tcarlin>
Component:	Installation - CloudForms	Assignee:	John Matthews <jmatthew>
Status:	NEW ---	QA Contact:	Sudhir Mallamprabhakara <smallamp>
Severity:	high	Docs Contact:	Dan Macpherson <dmacpher>
Priority:	unspecified
Version:	1.1	CC:	bthurber, qci-bugzillas
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:		Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	1724792

Description Thom Carlin 2017-03-13 19:31:34 UTC

Description of problem:

While investigating other issues, discovered /dev/vdb was not actually used by CloudForms setup by QCI

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

1.1

How reproducible:

100%

Steps to Reproduce:
1. Install/configure QCI
2. Deploy provider with CloudForms
3. ssh cloudforms_system
4. appliance_console
5. Examine Local Database Server line (and below)

Actual results:

Local Database Server:   not initialized
CFME Server:             running
CFME Database:           localhost
Database/Region:         vmdb_production / 1

Expected results:

Initialized database

Additional info:

Also checked /dev/vdb.  It was partitioned but not used (all nulls).

Probably also affects 1.0

Proposed solution: Pass "--dbdisk" parameter to appliance_console_cli

CloudForms appears to be operational but not correctly configured.

Comment 1 Kedar Kulkarni 2017-03-14 16:37:40 UTC

I recently installed CFME on top of OSP. 

I ran the following command: 
 od -c /dev/vdb

Output: 
od: /dev/vdb: No such file or directory

Comment 2 Thom Carlin 2017-03-14 16:44:23 UTC

My initial configuration was for RHV.  Please note that the database *was* configured -- the issue was not there.  The corrected steps 4/5 should be:
4. od -c /dev/vdb
5. df /var/opt/rh/rh-postgresql94/lib/pgsql/data [for 1.1]

Expected results:

4. Non-null data
5. /dev/mapper/vg_data-lv-pg [...] /var/opt/rh/rh-postgres94/lib/pgsql/data

Actual results:

4. Non-null data
5. /dev/mapper/VG--CFME-lv-var [...] /var 

Comment 1 reflects this -- QCI may need to add a second disk so both OpenStack and RHV are setup similarly.