Bug 608868 - API for retrieving action details is cumbersome
API for retrieving action details is cumbersome
Status: CLOSED NOTABUG
Product: Red Hat Satellite 5
Classification: Red Hat
Component: API (Show other bugs)
530
All Linux
low Severity medium
: ---
: ---
Assigned To: Tomas Lestach
Red Hat Satellite QA List
:
Depends On:
Blocks: 462714
  Show dependency treegraph
 
Reported: 2010-06-28 15:35 EDT by Aron Parsons
Modified: 2016-01-04 00:14 EST (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2010-07-16 14:56:15 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Aron Parsons 2010-06-28 15:35:59 EDT
There is not an easy way to get detailed output from an action.  The 'message' field from the schedule.* calls never contains any useful info.  The only way to get the detailed messages is to call system.listSystemEvents on each system you got from schedule.list{InProgress,Completed,Failed} and then filter it locally.

A call like schedule.getActionResults(session, actionID) which returns the detailed results of an action (e.g., installed package list, configuration file details) would be very useful.
Comment 1 Aron Parsons 2010-07-16 14:56:15 EDT
Invalid.

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