Bug 1385176

Summary: Configuring pglogical replication fails on the global region after setting up HA on a remote region
Product: Red Hat CloudForms Management Engine Reporter: Nick Carboni <ncarboni>
Component: ReplicationAssignee: Nick Carboni <ncarboni>
Status: CLOSED CURRENTRELEASE QA Contact: Alex Newman <anewman>
Severity: high Docs Contact:
Priority: unspecified    
Version: 5.7.0CC: anewman, cpelland, jhardy, obarenbo, simaishi
Target Milestone: GAKeywords: TestOnly
Target Release: 5.8.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: 5.8.0.0 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
: 1386788 (view as bug list) Environment:
Last Closed: 2017-06-12 17:18:24 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Bug Depends On:    
Bug Blocks: 1386788    

Description Nick Carboni 2016-10-14 21:16:39 UTC 
Description of problem:
After setting up repmgr HA on a remote region, attempting to create a subscription to that remote region on a global region fails with the following message:

Error during replication configuration save: Failed to save subscription to 192.168.211.154: Schema validation failed for host 192.168.211.154: Current schema tables do not match expected Additional tables in current schema: ["repl_events", "repl_monitor", "repl_nodes"] Missing tables in current schema: []

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

This is because we check the remote region's schema against the one stored in a file to be sure that they are compatible for replication.

This protects against trying to sync data from the remote region that won't have a corresponding table (or column) on the global region.

This check really only needs to apply to tables that we could possibly replicate.

We can soften the check to remove these tables as well as some others.
Comment 2 Nick Carboni 2016-10-18 20:49:11 UTC 
https://github.com/ManageIQ/manageiq/pull/12039
Comment 3 CFME Bot 2016-10-19 14:11:17 UTC 
New commit detected on ManageIQ/manageiq/master:
https://github.com/ManageIQ/manageiq/commit/617b96fea8d400eb92c80a6a205688e40765feee

commit 617b96fea8d400eb92c80a6a205688e40765feee
Author:     Nick Carboni <ncarboni>
AuthorDate: Tue Oct 18 16:43:06 2016 -0400
Commit:     Nick Carboni <ncarboni>
CommitDate: Wed Oct 19 08:56:45 2016 -0400

    Don't consider tables that are always excluded during the schema check
    
    This was causing pglogical to complain about the repmgr tables when
    a remote region was using HA and we tried to compare the schemas
    for compatibility.
    
    https://bugzilla.redhat.com/show_bug.cgi?id=1385176

 lib/evm_database.rb | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)
Comment 4 CFME Bot 2016-10-19 14:45:53 UTC 
New commit detected on ManageIQ/manageiq/euwe:
https://github.com/ManageIQ/manageiq/commit/e5dab27f7647588da9b047e818b3afc4930c9b7b

commit e5dab27f7647588da9b047e818b3afc4930c9b7b
Author:     Gregg Tanzillo <gtanzill>
AuthorDate: Wed Oct 19 10:08:55 2016 -0400
Commit:     Oleg Barenboim <chessbyte>
CommitDate: Wed Oct 19 09:40:44 2016 -0500

    Merge pull request #12039 from carbonin/ignore_always_excluded_tables_when_checking_schema
    
    Don't consider tables that are always excluded during the schema check
    (cherry picked from commit 35628ec434e5792f9f3343fd2c9233b11591acad)
    
    https://bugzilla.redhat.com/show_bug.cgi?id=1385176

 lib/evm_database.rb | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)