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 1331378

Summary: Sync optimization should be enhanced to check content counts
Product: Red Hat Satellite Reporter: Justin Sherrill <jsherril>
Component: Content ManagementAssignee: Stephen Benjamin <stbenjam>
Status: CLOSED DUPLICATE QA Contact: Katello QA List <katello-qa-list>
Severity: high Docs Contact:
Priority: unspecified    
Version: 6.2.0CC: bbuckingham, bkearney, jsherril, stbenjam, tpapaioa
Target Milestone: UnspecifiedKeywords: Performance, Triaged
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-02-19 18:59:15 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:

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 ***