+++ 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.
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.
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 8pulp-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.