Bug 1322066 - duplicate key error durring replication
Summary: duplicate key error durring replication
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: Replication
Version: 5.5.0
Hardware: All
OS: All
high
high
Target Milestone: GA
: 5.6.0
Assignee: Gregg Tanzillo
QA Contact: Alex Newman
URL:
Whiteboard: replication
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-03-29 17:33 UTC by Felix Dewaleyne
Modified: 2019-10-10 11:42 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-05-18 01:59:54 UTC
Category: ---
Cloudforms Team: ---
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Felix Dewaleyne 2016-03-29 17:33:23 UTC 
Created attachment 1141352 [details]
sydney_sync_trace.txt

Description of problem:
durring replication the error "ERROR:  duplicate key value violates unique constraint "index_miq_event_definitions_on_guid"" is thrown out


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

How reproducible:
all the time in multiple regions for the customer (cloudforms regions)

Steps to Reproduce:
1. this happens during replication
2.
3.

Actual results:
see attachemnts

Expected results:
replication completes

Additional info:
Comment 5 Nick Carboni 2016-05-16 17:52:13 UTC 
Both of the tickets related to this BZ are closed. Can this BZ be closed?
Comment 6 Gregg Tanzillo 2016-05-16 19:39:09 UTC 
Felix, per Nick's comment, can this BZ be closed?
Comment 7 Felix Dewaleyne 2016-05-17 09:31:53 UTC 
I would recommend to see with Jared who resolved the issues if anything should be raised here from the solution that was applied. I don't see many notes in the cases so I'm not sure what was done exactly to get the environments back up.
Comment 8 Jared Deubel 2016-05-18 01:59:54 UTC 
Yes we can close out this case. I will close it.
Note You need to log in before you can comment on or make changes to this bug.