Bug 465501 - ActivationKey.listConfigChannels returns incorrect types
Summary: ActivationKey.listConfigChannels returns incorrect types
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Satellite 5
Classification: Red Hat
Component: API
Version: 530
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Justin Sherrill
QA Contact: Sayli Karmarkar
URL:
Whiteboard:
Depends On:
Blocks: 456996
TreeView+ depends on / blocked
 
Reported: 2008-10-03 16:12 UTC by Justin Sherrill
Modified: 2015-03-23 01:09 UTC (History)
2 users (show)

Fixed In Version: sat530
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2009-09-10 19:53:26 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Justin Sherrill 2008-10-03 16:12:03 UTC
ActivationKey.listConfigChannels says it returns:

array:

    * struct - Configuration Channel Type information
          o int "id"
          o string "label"
          o string "name"
          o string "priority"


but in reality it returns:

array:

    * struct - Configuration Channel Type information
          o int "id"
          o string "label"
          o string "name"
          o struct "config_channel_type"
               - String priority
               - int i
               - String name
               - String label



Either the doc needs to be corrected, or the call needs to be fixed

Comment 1 Justin Sherrill 2008-10-29 19:27:05 UTC
4e9c75c..9286ea4

Comment 2 Sayli Karmarkar 2009-01-22 18:38:00 UTC
Verified on Satellite-5.3.0-RHEL5-re20081223.1. 
Original documentation error specified doesn't exist and I can see the result as 

[{'description': 'myconfig', 
  'configChannelType': 
        {'priority': 1, 
               'id': 1, 
             'name': 'A general purpose configuration channel', 
            'label': 'normal'}, 
  'label': 'myconfig', 
  'orgId': 1, 
  'id': 1, 
  'name': 'myconfig'}]

However, there is an additional variable "type" in the doc which is not used. Created a new bz #481200 for the same.

~SayliK

Comment 3 wes hayutin 2009-08-13 13:35:17 UTC
release pending

Comment 4 Brandon Perkins 2009-09-10 19:53:26 UTC
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

http://rhn.redhat.com/errata/RHEA-2009-1434.html


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