Project

General

Profile

Actions

Bug #22647

closed

Katello doesn't update sync notification URL on sync

Added by Stephen Benjamin over 6 years ago. Updated almost 6 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
Repositories
Target version:
Difficulty:
Triaged:
Fixed in Releases:
Found in Releases:

Description

Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=1545364

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.

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:

  1. 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:

  1. 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

Actions

Also available in: Atom PDF