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 1439230 - [RFE] Add API that returns individual steps of a foreman task
Summary: [RFE] Add API that returns individual steps of a foreman task
Keywords:
Status: CLOSED DUPLICATE of bug 1353414
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Tasks Plugin
Version: 6.2.8
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-04-05 13:20 UTC by Dennis Kliban
Modified: 2017-05-11 18:17 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-05-11 08:15:46 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Dennis Kliban 2017-04-05 13:20:36 UTC
This API is needed in order to determine which tasks on the capsule are responsible for the sync. This task information can tell the API user precise details of how the sync/publish tasks on the capsule went.

Comment 1 Dennis Kliban 2017-04-05 13:21:04 UTC
This would greatly help with automated testing of capsule syncs.

Comment 2 Ivan Necas 2017-05-11 08:15:46 UTC

*** This bug has been marked as a duplicate of bug 1353414 ***


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