Bug 600691 - errata.getDetails(session, name) doesn't return the errata ID
errata.getDetails(session, name) doesn't return the errata ID
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: sat540-api/sat540-apis
  Show dependency treegraph
 
Reported: 2010-06-05 12: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-14 15:02:13 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-05 12:35:26 EDT
Description of problem:
errata.getDetails() doesn't return the errata ID.  This would be useful for locating an errata and then looping to apply it to all the systems it affects via system.scheduleApplyErrata(). 

The workaround is to get a list of systems affected by the errata via errata.listAffectedSystems(), then call system.getRelevantErrata() on one of the systems returned, and then loop through the list of errata until you find a matching name and then get the errata ID from that data structure.

Version-Release number of selected component (if applicable):
Satellite 5.3.0

How reproducible:
Always

Steps to Reproduce:
1. call errata.getDetails(session, name)

Actual results:
the errata ID is not in the returned data structure

Expected results:
the errata ID should be in the returned data structure
Comment 1 Aron Parsons 2010-07-14 15:02:13 EDT
I guess this isn't needed.  I was just using the API inefficiently when I wrote this report.

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