Bug 1435341 - appliance_console on OpenStack image doesn't create database
Summary: appliance_console on OpenStack image doesn't create database
Keywords:
Status: CLOSED DUPLICATE of bug 1432469
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: Appliance
Version: 5.7.0
Hardware: All
OS: All
high
high
Target Milestone: GA
: cfme-future
Assignee: Gregg Tanzillo
QA Contact: luke couzens
URL:
Whiteboard: appliance:database:black
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-03-23 14:54 UTC by Christian Jung
Modified: 2018-02-12 12:25 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-04-19 19:31:08 UTC
Category: ---
Cloudforms Team: ---
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1432469 0 high CLOSED confusion around appliance_console database setup 2021-02-22 00:41:40 UTC

Internal Links: 1432469

Description Christian Jung 2017-03-23 14:54:56 UTC 
Description of problem:
When using the CFME image for OpenStack, the appliance_console tool doesn't properly create the database

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

How reproducible:
always, but ONLY with the OpenStack images

Steps to Reproduce:
1. deploy CFME image on OpenStack
2. start appliance_console
3. do initial setup

Actual results:
it doesn't create the DB properly and consequent steps fail

Expected results:
works as designed

Additional info:
after manually copying the database.yml file from another appliance, we were able to recover and complete the configuration
Comment 7 luke couzens 2017-03-31 11:13:10 UTC 
So I have tested this on 5.6 and 5.7 including 5.7.1.0 and I do not see this issue. Are we sure the appliance was not setup as a dedicated db by mistake?
Comment 9 Dave Johnson 2017-04-13 21:53:48 UTC 
Could be a dup of bug 1432469
Comment 10 Nick Carboni 2017-04-19 19:31:08 UTC 
I was also not able to reproduce this on 5.7.1.3

Closing as a duplicate of 1432469

*** This bug has been marked as a duplicate of bug 1432469 ***
Note You need to log in before you can comment on or make changes to this bug.