Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 1017350

Summary: [RFE] need a way to tell if a Pulp server's repo is out of sync.
Product: Red Hat Satellite Reporter: Eric Helms <ehelms>
Component: PulpAssignee: satellite6-bugs <satellite6-bugs>
Status: CLOSED WORKSFORME QA Contact: Katello QA List <katello-qa-list>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 6.0.2CC: bbuckingham, bkearney, bmbouter, daviddavis, dkliban, ggainey, ipanova, jsherril, mhrivnak, mmccune, omaciel, pcreech, rchan, ttereshc
Target Milestone: UnspecifiedKeywords: FutureFeature
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: 976439 Environment:
Last Closed: 2017-02-20 02:51:33 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:
Embargoed:
Bug Depends On: 976439    
Bug Blocks: 950746    

Description Eric Helms 2013-10-09 17:13:09 UTC 
+++ This bug was initially created as a clone of Bug #976439 +++

Description of problem:

Katello needs a way to know if a repo on a pulp node is out of sync with its upstream repo.  Potentially knowing what is out of sync would be nice, but just knowing that it is out of sync is needed.
Comment 5 Brad Buckingham 2016-08-03 20:15:51 UTC 
In Satellite 6.2, the Capsule has moved away from being a Pulp Node to an actual Pulp Server.  That said, there isn't an easy way to determine if the server and capsule are out of sync.
Comment 6 Brad Buckingham 2016-11-21 16:58:28 UTC 
Created redmine issue http://projects.theforeman.org/issues/17419 from this bug
Comment 7 Michael Hrivnak 2017-02-20 02:51:33 UTC 
Brad, I think we've accomplished this recently with the work to be smarter about when to sync and publish a capsule repo. I think that since Pulp makes this info available about a repo:

last unit added
last unit removed
last publish time
last sync time

... Katello is able to know when a repo on a capsule is behind the corresponding repo on the Satellite.

Feel free to re-open if there's more you'd like to see.

FWIW the concept of versioned repos, which will debut in some release of Pulp 3.y (I'll push for 3.0 but can't promise yet), will help tremendously.
Comment 8 pulp-infra@redhat.com 2019-06-27 12:12:22 UTC 
The Pulp upstream bug status is at CLOSED - WONTFIX. Updating the external tracker on this bug.