Bug 1331378 - Sync optimization should be enhanced to check content counts
Summary: Sync optimization should be enhanced to check content counts
Keywords:
Status: CLOSED DUPLICATE of bug 1309384
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Content Management
Version: 6.2.0
Hardware: Unspecified
OS: Unspecified
unspecified
high vote
Target Milestone: Unspecified
Assignee: Stephen Benjamin
QA Contact: Katello QA List
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-04-28 12:12 UTC by Justin Sherrill
Modified: 2019-12-16 05:43 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-02-19 18:59:15 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description Justin Sherrill 2016-04-28 12:12:51 UTC
Description of problem:

Currently if during syncing nothing no new units were added or updated we skip things such as indexing.  This can lead to problems where one sync failed (but imported a bunch of units) so post sync actions are skipped.  On the next sync there are no units and so we skip indexing.  

We should use the counts of the items in the repo to not skip indexing.


Version-Release number of selected component (if applicable):


How reproducible:
Always


Not easy to reproduce, but this should work:

Steps to Reproduce:
1. Create and sync a repo
2. Using pulp-admin watch for the repo publish to start and cancel it
3. Re-sync the repo

Actual results:
After the resync the repo will show in the UI as having no content


Expected results:
After resync content counts are correct

Comment 3 Justin Sherrill 2016-06-07 17:36:43 UTC
It was added to 6.1, this bz was suggested we alter the behaviour to be smarter.  

Right now the user has to recognize what is going on and flip a setting (force_post_sync_actions) and sync again.

Comment 4 Bryan Kearney 2016-07-26 15:25:24 UTC
Moving 6.2 bugs out to sat-backlog.

Comment 5 Bryan Kearney 2016-07-26 15:29:18 UTC
Moving 6.2 bugs out to sat-backlog.

Comment 7 Stephen Benjamin 2018-02-19 18:59:15 UTC

*** This bug has been marked as a duplicate of bug 1309384 ***


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