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 834036 - Inconsistency in sync status view via sync mgmt and Dashboard sync overview for very large repos
Summary: Inconsistency in sync status view via sync mgmt and Dashboard sync overview f...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: WebUI
Version: 6.0.1
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: Unspecified
Assignee: Justin Sherrill
QA Contact: Kedar Bidarkar
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-06-20 17:19 UTC by Kedar Bidarkar
Modified: 2014-03-18 17:38 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-03-18 17:38:35 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
Status as 100% from Sync DashBoard (163.90 KB, image/png)
2012-06-20 17:21 UTC, Kedar Bidarkar 		no flags Details
Status not as 'Sync Complete' under Sync Mgmt (134.23 KB, image/png)
2012-06-20 17:22 UTC, Kedar Bidarkar 		no flags Details
View All

Description Kedar Bidarkar 2012-06-20 17:19:26 UTC 
Description of problem:

There is inconsistency between what sync status view is via 

Sync Management  and 
Dashboard Sync Overview.

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

How reproducible:
Try syncing large repos and towards the end of the sync, we can observe this 
inconsistency issue.

Steps to Reproduce:
1. sync large repos like http://download.devel.redhat.com/released/F-15/GOLD/Everything/x86_64/os/
2.
3.

DashBoard Sync Overview shows, the sync has completed "100%", But

Sync Mgmt does not show, the status as "Sync Complete"

From the above 2 different states, I feel there is some inconsistency for the state of syncs for very large repos.

I will be attaching the screen-shots shortly.

Build : 2012-06-18.1/  
RAM : 2GB
SWAP : 2GB
REPO synced : Single repo F17 (27.1 GB)
  
Actual results:

Inconsistency in sync status

Expected results:


Additional info:
Comment 1 Kedar Bidarkar 2012-06-20 17:21:39 UTC 
Created attachment 593280 [details]
Status as 100% from Sync DashBoard
Comment 2 Kedar Bidarkar 2012-06-20 17:22:27 UTC 
Created attachment 593281 [details]
Status not as 'Sync Complete' under Sync Mgmt
Comment 3 Kedar Bidarkar 2012-06-20 17:26:05 UTC 
The below comment is from Ivan Necas.
https://bugzilla.redhat.com/show_bug.cgi?id=828977#c11

The problem is the progress shows the ratio of downloaded/all packages. But it doesn't include the time required:

1. for calculating metadata
2. removing orphaned packages. 

Both actions take quite a lot of time (I know that calculating metadata for large repo can take 2+ hours. The important thing is that it finished at the end and doesn't get canceled (what this BZ is about). There are already some activities on the Pulp side to improve generating manifests: right now it's using createrepo utility, that doesn't provide the progress information. I don't thing this issues are worth z-stream.
Comment 5 Mike McCune 2013-08-16 18:11:58 UTC 
getting rid of 6.0.0 version since that doesn't exist
Comment 6 Mike McCune 2014-03-18 17:38:35 UTC 
This bug was closed because of a lack of activity.  If you feel this bug should be reconsidered for attention please feel free to re-open the bug with a comment stating why it should be reconsidered.
Note You need to log in before you can comment on or make changes to this bug.