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 746659 - Sync status remains in 'Queued' state for scheduled sync
Summary: Sync status remains in 'Queued' state for scheduled sync
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: WebUI
Version: 6.0.0
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: Unspecified
Assignee: Shannon Hughes
QA Contact: Katello QA List
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-10-17 12:48 UTC by Sachin Ghai
Modified: 2019-09-26 13:22 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-08-22 18:01:37 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
sync status set as 'queued' (33.57 KB, image/png)
2011-10-17 12:49 UTC, Sachin Ghai 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 808334 0 unspecified CLOSED Sync status remains in 'Queued', however sync is finished at backend 2021-02-22 00:41:40 UTC

Internal Links: 808334

Description Sachin Ghai 2011-10-17 12:48:28 UTC 
Description of problem:
I started a scheduled sync for a repo. The defined sync plan is to start the sync on daily at 5:30 PM IST.

As per pulp logs sync initiated at its correct time.

-----
2011-10-17 17:30:01,401 3524:140224499803904: pulp.server.api.repo_sync:INFO: repo_sync:244 Sync invoked for repo <sghai_org-aeolus-aeolus_x86_64>
2011-10-17 17:30:01,467 3524:140224499803904: pulp.server.api.repo_sync:INFO: repo_sync:258 Sync of sghai_org-aeolus-aeolus_x86_64 starting, skip_dict = {}
2011-10-17 17:30:01,476 3524:140224499803904: pulp.server.api.synchronizers:INFO: synchronizers:540 cacert = <None>, cert = <None>
2011-10-17 17:30:01,476 3524:140224499803904: pulp.server.api.synchronizers:INFO: synchronizers:588 Fetching repo to </var/lib/pulp//repos/sghai_org/Locker/aeolus/aeolus_x86_64> with verify_options <{'checksum': True, 'size': True}>
2011-10-17 17:30:43,921 3524:140224499803904: pulp.server.api.synchronizers:INFO: synchronizers:608 Running createrepo, this may take a few minutes to complete.
-----

 However Katello UI is showing the sync status as 'queued'. and this remains in queued state. See the attachement1. 


I checked from katello-cli, CLI showing the state as 'waiting'.
katello> repo status --name=aeolus_x86_64 --product=aeolus --org=sghai_org
--------------------------------------------------------------------------------
                               Repository Status
--------------------------------------------------------------------------------

Id:            sghai_org-aeolus-aeolus_x86_64
Name:          aeolus_x86_64
Package Count: 226
Last Sync:     2011/10/17 17:31:24
Sync State:    Waiting
Progress:      0% done (0 of 0 packages downloaded)



Version-Release number of selected component (if applicable):
[root@dhcp201-158 ~]# rpm -qa | grep katello
katello-cli-0.1.10-1.git.712.be6830e.fc15.noarch
katello-0.1.93-1.git.0.6934d37.fc15.noarch
katello-all-0.1.93-1.git.0.6934d37.fc15.noarch
katello-configure-0.1.6-1.git.5.76ba627.fc15.noarch
katello-repos-0.1.3-1.git.0.db2bd1d.fc15.noarch
[root@dhcp201-158 ~]# rpm -qa | grep pulp
pulp-common-0.0.237-5.fc15.noarch
pulp-0.0.237-5.fc15.noarch
m2crypto-0.21.1.pulp-5.fc15.x86_64


How reproducible:
always

Steps to Reproduce:
1. Define a sync plan ( daily sync at specified time)
2. Applied this sync plan to product
3. Now check the sync status when sync initiated at specified scheduled time
  
Actual results:
Sync staus remains in 'Queued' state

Expected results:
Sync should run and status should be automatically changed from queued ==> running ==> finish

Additional info:
Comment 1 Sachin Ghai 2011-10-17 12:49:21 UTC 
Created attachment 528529 [details]
sync status set as 'queued'
Comment 2 Mike McCune 2012-01-26 19:38:03 UTC 
mass move to CFSE product.
Comment 3 Shannon Hughes 2012-01-30 19:12:57 UTC 
can you retest this one. i was not seeing queued state, rather ui was showing sync progress as zero. when the sync kicked in, the status bar jumped quickly since the gap between the check and the sync complete occured. then subsequent checks on the status shows as finished.

my guess is this was fixed since october.
Comment 4 Sachin Ghai 2012-02-01 08:51:37 UTC 
Yes, I retested this again on new katello build.

And now I'm not getting the sync status as 'queued' however UI is showing a empty progress bar. This needs to be fixed. I'll file another bug for this issue.

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