Bug 1620884 - Unable to start DB replicated CFME
Summary: Unable to start DB replicated CFME
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: Appliance
Version: 5.10.0
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: GA
: cfme-future
Assignee: Nick Carboni
QA Contact: Dave Johnson
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-08-23 12:00 UTC by Jaroslav Henner
Modified: 2018-08-23 13:19 UTC (History)
3 users (show)

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


Attachments (Terms of Use)
journalctl -xe (17.27 KB, text/plain)
2018-08-23 12:00 UTC, Jaroslav Henner
no flags Details

Description Jaroslav Henner 2018-08-23 12:00:58 UTC
Created attachment 1478144 [details]
journalctl -xe

Description of problem:
After configuring server A as primary and B as stand-by, evmd cannot be started on any of them. There is a problem related to DB structure in the log.

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

How reproducible:
2/2

Steps to Reproduce:
1. Create db on A
2. Configure A as primary server for replication
3. Configure B as stand-by
4. Try starting evmserverd

Actual results:
hat.com sh[2963]: PG::UndefinedTable: ERROR:  relation "miq_servers" does not exist
hat.com sh[2963]: LINE 8:                WHERE a.attrelid = '"miq_servers"'::regclass


Expected results:
evmd started

Additional info:

Comment 2 Nick Carboni 2018-08-23 13:19:40 UTC
I was able to configure HA using the images for 5.10.0.11 without issue.

Please ensure you are following the documentation for configuring HA here https://access.redhat.com/documentation/en-us/red_hat_cloudforms/4.6/html/high_availability_guide/installation

Closing this as WORKSFORME. Please reopen with the full version of the image you used and a complete set of reproduction steps if you think this is still an issue.

Additionally, if you have a system where the issue currently exists in the Red Hat QE network please add a private comment with the ip addresses of the appliances so we can debug the issue.


Note You need to log in before you can comment on or make changes to this bug.