| Summary: | Replication fails to start after 5.5 -> 5.6 migration | ||
|---|---|---|---|
| Product: | Red Hat CloudForms Management Engine | Reporter: | luke couzens <lcouzens> |
| Component: | Appliance | Assignee: | Gregg Tanzillo <gtanzill> |
| Status: | CLOSED ERRATA | QA Contact: | luke couzens <lcouzens> |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | 5.6.0 | CC: | abellott, cpelland, gtanzill, jhardy, lcouzens, obarenbo, simaishi |
| Target Milestone: | GA | ||
| Target Release: | 5.6.0 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | replication:migration:upgrade | ||
| Fixed In Version: | 5.6.0.8 | Doc Type: | Bug Fix |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2016-06-29 15:55:29 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: | |
|
Description
luke couzens
2016-04-27 14:49:58 UTC
Hey gregg, So unfortunately I don't have the appliance's anymore however I am just going to provision some new ones for us to take a look at. I will send you the ip's once its ready. (unless it works this time) ;) Just ran through beta1 to beta2 and running bin/rails r tools/purge_duplicate_rubyrep_triggers.rb that seemed to do the trick for that replication so I will let you know. Cheers. The same or similar issue is also present in an in-place upgrade from 5.5 to 5.6.0.7-beta2.6 New commit detected on ManageIQ/manageiq/master: https://github.com/ManageIQ/manageiq/commit/b2838bd65a278470c8b7bc8315aac6b375df5d62 commit b2838bd65a278470c8b7bc8315aac6b375df5d62 Author: Gregg Tanzillo <gtanzill> AuthorDate: Fri May 20 13:02:01 2016 -0400 Commit: Gregg Tanzillo <gtanzill> CommitDate: Fri May 20 14:03:02 2016 -0400 Explicitly add internal Rails tables to replication excluded tables list https://bugzilla.redhat.com/show_bug.cgi?id=1331053 lib/miq_pglogical.rb | 2 +- lib/miq_rubyrep.rb | 1 + spec/replication/util/miq_pglogical_spec.rb | 2 +- 3 files changed, 3 insertions(+), 2 deletions(-) Luke, I took a look at your region 0 appliance and saw that the replication worker is stuck in a loop of stopping due to exceeding the memory threshold and then starting again. Here's one of the log messages: [----] W, [2016-06-03T09:27:10.677516 #11463:1323998] WARN -- : MIQ(MiqServer#validate_worker) Worker [MiqReplicationWorker] with ID: [794], PID: [29987], GUID: [d7009c50-298e-11e6-8075-fa163e3af26a] process memory usage [274493000] exceeded limit [209715200], requesting worker to exit This has been fixed by Nick in this PR - https://github.com/ManageIQ/manageiq/pull/9087 I went into the advanced settings on you appliance and added the new threshold, reset replication and now the worker is replicating successfully. Thanks for your help Gregg. Verified in 5.6.0.8 Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2016:1348 |