Red Hat Bugzilla – Bug 1216234
GET /api/v2/locations/:id does not return information about realms
Last modified: 2016-07-27 04:50:41 EDT
Description of problem: A location can be associated with zero or more realms. The API documentation makes mention of this in the documentation for POST /api/v2/locations and PUT /api/v2/locations/:id, and the UI exposes this capability too. (See the relevant API documentation page at https://sat.example.com/apidoc/v2/locations.html and search for "realm".) However, a GET request to /api/v2/locations/:id will return information about associated realms. 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: 1. Issue an HTTP GET request to https://sat.example.com/api/v2/locations/:id 2. Examine the response. 3. Discover that realms are not mentioned. Actual results: [ 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', ] Expected results: Same as above, but with realms mentioned. Additional info:
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.
Yes, bug. Realms should have been added to API response for locs/orgs when introduced
Created redmine issue http://projects.theforeman.org/issues/10357 from this bug
Upstream bug component is Multi Org
*** Bug 1230873 has been marked as a duplicate of this bug. ***
Moving to POST since upstream bug http://projects.theforeman.org/issues/10357 has been closed ------------- Ondřej Pražák Applied in changeset commit:502feabe1259186625453a9dcc2165ccd0292741.
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