Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
Description of problem:
The API returns significantly different information for the following two calls:
* POST /api/v2/locations
* GET /api/v2/locations/:id
This is problematic for two reasons:
* This is inconsistent with how other paths behave, which makes writing client code harder to do.
* Getting authoritative information about a just-created location requires a follow-up API call, which is time-consuming.
Version-Release number of selected component (if applicable):
Tested against Satellite-6.1.0-RHEL-6-20150424.0 and Satellite-6.1.0-RHEL-7-20150424.0.
How reproducible:
100%
Steps to Reproduce:
Here's a sample script:
>>> from nailgun import entities
>>> loc_attrs = entities.Location().create_json()
>>> loc_attrs2 = entities.Location(id=loc_attrs['id']).read_json()
>>> loc_attrs.keys() # contents of response to POST call
[
u'ancestry',
u'apply_info_task_id',
u'created_at',
u'default_info',
u'description',
u'id',
u'ignore_types',
u'katello_default',
u'label',
u'name',
u'title',
u'updated_at',
]
>>> loc_attrs2.keys() # contents of response to GET call
[
u'compute_resources',
u'config_templates',
u'created_at',
u'description',
u'domains',
u'environments',
u'hostgroups',
u'id',
u'media',
u'name',
u'organizations',
u'parameters',
u'select_all_types',
u'smart_proxies',
u'subnets',
u'title',
u'updated_at',
u'users',
]
Actual results:
The actual results are as shown in the above example.
Expected results:
Both POST and GET requests should return the same information.
Additional info:
Comment 1RHEL Program Management
2015-04-28 20:33:19 UTC
Since this issue was entered in Red Hat Bugzilla, the release flag has been
set to ? to ensure that it is properly evaluated for this release.
Comment 3jmagen@redhat.com
2015-05-03 12:53:00 UTC
This was a known issue that the response of POST/PUT is just the object and it doesn't use a RABL template (render :json => @object), whereas the GET :id included all the relationships which are in the RABL template show.json.rabl
Moving to POST since upstream bug http://projects.theforeman.org/issues/10356 has been closed
-------------
alon goldboim
Applied in changeset commit:d575926a689fd6abd6f26ee2823ce95eef07dd38.
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.
https://access.redhat.com/errata/RHBA-2016:1500
Description of problem: The API returns significantly different information for the following two calls: * POST /api/v2/locations * GET /api/v2/locations/:id This is problematic for two reasons: * This is inconsistent with how other paths behave, which makes writing client code harder to do. * Getting authoritative information about a just-created location requires a follow-up API call, which is time-consuming. Version-Release number of selected component (if applicable): Tested against Satellite-6.1.0-RHEL-6-20150424.0 and Satellite-6.1.0-RHEL-7-20150424.0. How reproducible: 100% Steps to Reproduce: Here's a sample script: >>> from nailgun import entities >>> loc_attrs = entities.Location().create_json() >>> loc_attrs2 = entities.Location(id=loc_attrs['id']).read_json() >>> loc_attrs.keys() # contents of response to POST call [ u'ancestry', u'apply_info_task_id', u'created_at', u'default_info', u'description', u'id', u'ignore_types', u'katello_default', u'label', u'name', u'title', u'updated_at', ] >>> loc_attrs2.keys() # contents of response to GET call [ u'compute_resources', u'config_templates', u'created_at', u'description', u'domains', u'environments', u'hostgroups', u'id', u'media', u'name', u'organizations', u'parameters', u'select_all_types', u'smart_proxies', u'subnets', u'title', u'updated_at', u'users', ] Actual results: The actual results are as shown in the above example. Expected results: Both POST and GET requests should return the same information. Additional info: