Bug 1391187 - pglogical replication fails to start after migration from 5.5 to 5.7
Summary: pglogical replication fails to start after migration from 5.5 to 5.7
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: Appliance
Version: 5.7.0
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: GA
: 5.8.0
Assignee: Nick Carboni
QA Contact: luke couzens
URL:
Whiteboard: black:upgrade:migration
Depends On:
Blocks: 1395387
TreeView+ depends on / blocked
 
Reported: 2016-11-02 18:09 UTC by luke couzens
Modified: 2017-06-12 17:13 UTC (History)
6 users (show)

Fixed In Version: 5.8.0.0
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1395387 (view as bug list)
Environment:
Last Closed: 2017-06-12 17:13:49 UTC
Category: ---
Cloudforms Team: ---
Target Upstream Version:


Attachments (Terms of Use)

Description luke couzens 2016-11-02 18:09:07 UTC
Description of problem:pglogical replication fails to start after migration from 5.5 to 5.7


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


How reproducible:100%


Steps to Reproduce:
1.setup rubyrep on 2 x 5.5 appliances
2.stop replication
3.upgrade to 5.7 using repos[0] and yum update
4.upgrade postgres to latest using miq_postgres_upgrade script
5.make edits to relevant files for pglogical following [1]
6.setup pglogical

Actual results:replication fails to replicate


Expected results:replication works correctly


Additional info:
[0]https://mojo.redhat.com/docs/DOC-1094760
[1]https://mojo.redhat.com/docs/DOC-1089985

Comment 2 Nick Carboni 2016-11-03 13:46:52 UTC
This failed because of a unique constraint violation during the initial sync for the pglogical subscription.

When a user moves from rubyrep to pglogical they should do a `bin/rake evm:dbsync:uninstall` *before* `yum update` to ensure all of the region's data is removed from the global.

Failing that I opened a PR to remove all of the region's data from the global region as a part of creating the subscription.

https://github.com/ManageIQ/manageiq/pull/12358

Comment 5 luke couzens 2017-03-06 12:39:53 UTC
Verified in 5.8.0.3


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