Red Hat Bugzilla – Bug 1308430
Cleaning up old tasks, sync status wrongly shows repos "Never synced"
Last modified: 2017-02-15 02:11:54 EST
Description of problem:
Applying patch from bz1289384, and running the cleanup script with AFTER=.. longer than a repo has been synced, Sync Status page shows the repo has not been synced ever.
I suggest this improvement: in case "Never synced" is about to appear, check if pulp repo has been synced, i.e. by running:
pulp-admin repo tasks list --repo-id <id>
(and finding newest sync operation)
or by querying repo_sync_results collection in mongodb (somehow via pulp, I guess)
Version-Release number of selected component (if applicable):
Sat6.2 / Sat6.1.6 patched by bz1289384 (foreman-tasks commit fb88f07)
Steps to Reproduce:
1. Sync a repo >1 day ago
2. foreman-rake foreman_tasks:cleanup AFTER=1d FILTER=
3. Check Sync status in WebUI
3. shows the repo "Never synced"
3. to show same info like before (without the cleanup script called)
kudos to Nikola Stiasni who discovered this bug.
Moving 6.2 bugs out to sat-backlog.
Would it not make sense to maintain the sync status as part of the metadata of
(In reply to Stuart Auchterlonie from comment #5)
> Would it not make sense to maintain the sync status as part of the metadata
> the repository?
I think repository metadata are generated only when publishing the repository, what is a different pulp action than repo sync. It usually (always?) follows repo sync, though.
Moreover, repo metadata are AFAIK just written to the disk under /var/lib/pulp and just pulp knows the proper location. It would be weird to get info about latest repo sync (katello request) from something written by pulp to the disk..
Here's me thinking we stored that info in the database somewhere :)