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 1199150 - Adding or removing products from a syncplan should return a task
Summary: Adding or removing products from a syncplan should return a task
Keywords:
Status: CLOSED DEFERRED
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: API
Version: 6.1.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: Katello QA List
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-03-05 14:30 UTC by jaudet
Modified: 2021-07-22 07:39 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-03-22 20:20:04 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description jaudet 2015-03-05 14:30:30 UTC
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 1 RHEL 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.

Comment 4 jaudet 2015-03-05 14:59:49 UTC
An automated test for this bug has been implemented. See: https://github.com/SatelliteQE/robottelo/pull/1969

Comment 5 jaudet 2015-03-05 15:05:10 UTC
Similar to: https://bugzilla.redhat.com/show_bug.cgi?id=1166365

Comment 6 Bryan Kearney 2016-07-08 20:32:34 UTC
Per 6.3 planning, moving out non acked bugs to the backlog

Comment 8 Bryan Kearney 2017-03-22 20:20:04 UTC
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.


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