Summary 2: Cloned Satellites will still make API callbacks into the Source Satellite via the sync_complete API. This causes task errors due to lock contention and should be prevented at all costs.

** First Issue: When cloning a Satellite there is a configuration in  /etc/foreman/plugins/katello.yaml that points to a URL end point:

   :post_sync_url: https://clone.example.com/katello/api/v2/repositories/sync_complete?token=wI7kAQtK87EBdlLbdVp1R1GLpWpsbiHj

this gets properly updated during the clone process. 

The issue is that this change is never properly updated at the Mongo/Pulp level and the old hostname will persist in the event_notifier database entry, note the URL is not that of the new cloned Satellite:

#  echo "db.event_listeners.find()" | mongo pulp_database

{ "_id" : ObjectId("20B3G0ppQ49r9xR00a"), "notifier_config" : { "url" : "https://production-satellite.example.com/katello/api/v2/repositories/sync_complete?token=R27Jp95A1drsJ7oER27Jp95A1drsJ7oE" }, "_ns" : "event_listeners", "event_types" : [ "repo.sync.finish" ], "id" : "3HkpvGemRtq2ISm83411", "notifier_type_id" : "http" }

** Second Issue: The cloned Satellite will often have 2 event_listener rows in the database. This causes *multiple* API calls to be made to either the production source Satellite or if the hostname was correct, the clone itself. 

This can be found by running:

# echo "db.event_listeners.find().count()" | mongo pulp_database
MongoDB shell version: 2.6.11
connecting to: pulp_database
2

If the count is > 1, we have an error condition where there are too many event_listeners