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 - [RFE] need a way to tell if a Pulp server's repo is out of sync.
Summary: [RFE] need a way to tell if a Pulp server's repo is out of sync.
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Pulp
Version: 6.0.2
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: Katello QA List
URL:
Whiteboard:
Depends On: 976439
Blocks: sat6-pulp-future
TreeView+ depends on / blocked
 
Reported: 2013-10-09 17:13 UTC by Eric Helms
Modified: 2021-04-06 18:27 UTC (History)
14 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of: 976439
Environment:
Last Closed: 2017-02-20 02:51:33 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 17419 0 None None None 2016-11-21 16:58:32 UTC
Pulp Redmine 199 0 Normal CLOSED - WONTFIX Need a way to tell if a Pulp server repo is out of sync with another Pulp server 2019-06-27 12:12:21 UTC

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.


Note You need to log in before you can comment on or make changes to this bug.