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:
Adding or removing products from a sync plan is an asynchronous task, and there's no way to monitor the progress of the task. This bites the user when:
* The user adds a product to a sync plan, then attempts to add that same product to a second sync plan.
* The user adds a product to a sync plan, removes it from the sync plan, then re-adds it.
* More scenarios?
This problem is exacerbated by the fact that product addition and deletion can take tens of seconds to complete. The solution? When a product is added to or removed from a sync plan, the satellite should return a task that can be monitored.
Version-Release number of selected component (if applicable):
How reproducible:
Very frequent, but varies depending on server load.
Steps to Reproduce:
Issue an HTTP PUT request to the following URLs. Pass in an identical list of product IDs as the JSON payload to each request:
* https://${hostname}/katello/api/v2/organizations/:organization_id/sync_plans/:sync_plan_id/add_products
* https://${hostname}/katello/api/v2/organizations/:organization_id/sync_plans/:sync_plan_id/remove_products
* https://${hostname}/katello/api/v2/organizations/:organization_id/sync_plans/:sync_plan_id/add_products
Actual results:
The server responds to product addition and removal requests with a hash of data about the sync plan being worked with.
Expected results:
The server responds to product addition and removal requests with a hash of data about the task under way.
Additional info:
Comment 1RHEL Program Management
2015-03-05 14:43:13 UTC
Since this issue was entered in Red Hat Bugzilla, the release flag has been
set to ? to ensure that it is properly evaluated for this release.
I do not believe this will be addressed in the next few releases, so I am closing this out. If you feel this was incorrect, please feel free to re-open with additional information.