Bug 997868 - sync.master.addToMaster have param id with type "long", but sync.master.create returns id as "int"
Summary: sync.master.addToMaster have param id with type "long", but sync.master.creat...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Satellite 5
Classification: Red Hat
Component: API
Version: 560
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: ---
Assignee: Tomas Lestach
QA Contact: Jan Hutař
URL:
Whiteboard:
Depends On:
Blocks: sat560-api sat560-blockers
TreeView+ depends on / blocked
 
Reported: 2013-08-16 10:39 UTC by Jan Hutař
Modified: 2013-10-01 21:44 UTC (History)
3 users (show)

Fixed In Version: spacewalk-java-2.0.2-22
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-10-01 21:44:58 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Jan Hutař 2013-08-16 10:39:32 UTC
Description of problem:
Looking into API documentation, there is a discrepancy in types ID parameters/result fields have in API documentation for sync.master.addToMasterand ...create functions.


Version-Release number of selected component (if applicable):
spacewalk-java-2.0.2-15.el5sat


How reproducible:
always


Steps to Reproduce:
1. Check https://<fqdn>/rhn/apidoc/handlers/MasterHandler.jsp#addToMaster
   and ...#create


Actual results:
One contains:
  long id - Id of the desired Master
second one have:
  int "id"


Expected results:
Types should be in sync


Additional info:
Maybe this is just a typo in documentation or something. It just seems strange.

Comment 1 Tomas Lestach 2013-08-19 11:55:42 UTC
spacewalk.git: 2eaba465d5cff4aed7a5979634fe82c4b6da321d

Comment 5 Clifford Perry 2013-10-01 21:40:43 UTC
Satellite 5.6 has been released. This bug was tracked under the release.  

This bug was either VERIFIED or RELEASE_PENDING (re-verified prior shortly
before release). 

Moving to CLOSED CURRENT_RELEASE. 

Text from Upgrade Erratum follows:

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHEA-2013-1395.html


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