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 771337 - Sync portlet doesn't show latest sync in some cases
Summary: Sync portlet doesn't show latest sync in some cases
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: WebUI
Version: 6.0.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: Unspecified
Assignee: Shannon Hughes
QA Contact: Katello QA List
URL:
Whiteboard:
Depends On:
Blocks: katello-sync-mgmt
TreeView+ depends on / blocked
 
Reported: 2012-01-03 12:06 UTC by Jeff Weiss
Modified: 2019-09-26 13:27 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-02-01 14:53:41 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Jeff Weiss 2012-01-03 12:06:00 UTC 
Description of problem:


Version-Release number of selected component (if applicable):
katello-0.1.157-1.git.2.6d49788.el6.noarch

How reproducible:


Steps to Reproduce:
1. Create a custom provider/product
2. Add a repo with a bad URL (that will give 404 for the repomd.xml file)
3. Sync the repo (will get error, portlet will show the failed sync).
4. Add a new repo to the same product with a good URL
5. Sync that new repo, wait for it to finish
6. Go to dashboard

Actual results:
Last result shown is the failed sync, successful one not shown

Expected results:
all results shown

Additional info:
Comment 1 Mike McCune 2012-01-26 19:38:15 UTC 
mass move to CFSE product.
Comment 2 Shannon Hughes 2012-01-31 21:37:14 UTC 
the algorithm is to always show critical errors if a specific repo did not sync correctly. so if you have four repos, three of which were successful and one that was not, the product status will remain in an error state on the dashboard. 

would like to close this as notabug as this is how the product sync status was designed.
Note You need to log in before you can comment on or make changes to this bug.