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.
Description of problem:
I defined a sync plan and applied on a product. When I checked the sync status, the progress bar was showing as empty (progress bar at 0 level). Sync started at it schedule interval, however even after sync completion, the empty progress bar was remains there.
Version-Release number of selected component (if applicable):
katello-0.1.206-1.el6.noarch
pulp-0.0.263-1.el6.noarch
katello-glue-pulp-0.1.206-1.el6.noarch
How reproducible:
always
Steps to Reproduce:
1. create a sync plan
2. Applied on product
3. check sync status
Actual results:
Empty progress bar before the sync starts and after sync finishes
Expected results:
No empty progress bar should be there on UI before its schedule interval and after sync completes.
Additional info:
we are checking for not running states and missed the queued state. added the queued state (waiting) to our list.
with this fix and how you render the page (refresh or wait for sync status) you will either see sync finished or queued. when the page is loaded we make calls to pulp to find out the latest status and if the repo is scheduled and waiting to run then the queued state will show.
note: please test this when 786762 is fixed and in modified state. this bug is blocking the correct behavior 786376