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'm not completely sure what triggers this, either the repo being small, or having two repos with the same URL or both put together.
Version-Release number of selected component (if applicable):
katello-0.1.236-1.git.10.516316b.el6.noarch
How reproducible:
always
Steps to Reproduce:
1. Create a provider/product/repo, with this repo url:
http://hudson.rhq.lab.eng.bos.redhat.com:8080/hudson/job/subscription-manager_master.el6/lastSuccessfulBuild/artifact/rpms/x86_64
2. Create a second provider/product/repo, use the same repo URL.
3. Sync the first repo (success)
4. Re-navigate to the sync status page
5. Sync the 2nd repo
Actual results:
"Complete" never shows up. The progress bar may appear briefly, but regardless, there is no final status until the page is refreshed. In some cases you'll even see the progress bar start up for both the first and second repo.
Expected results:
Only rows selected for sync are updated, final status shown when sync in complete, without reloading page.
Additional info: