Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1216234 - GET /api/v2/locations/:id does not return information about realms
GET /api/v2/locations/:id does not return information about realms
Status: CLOSED ERRATA
Product: Red Hat Satellite 6
Classification: Red Hat
Component: Organizations and Locations (Show other bugs)
6.1.0
Unspecified Unspecified
unspecified Severity unspecified (vote)
: Beta
: Unused
Assigned To: satellite6-bugs
Chris Duryee
http://projects.theforeman.org/issues...
: Triaged
: 1230873 (view as bug list)
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2015-04-28 16:19 EDT by jaudet
Modified: 2016-07-27 04:50 EDT (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2016-07-27 04:50:41 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Foreman Issue Tracker 10357 None None None 2016-04-22 11:33 EDT
Red Hat Product Errata RHBA-2016:1500 normal SHIPPED_LIVE Red Hat Satellite 6.2 Base Libraries 2016-07-27 08:24:38 EDT

  None (edit)
Description jaudet 2015-04-28 16:19:17 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:
Comment 1 RHEL Product and Program Management 2015-04-28 16:33:21 EDT
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 3 jmagen@redhat.com 2015-05-03 08:53:33 EDT
Yes, bug. Realms should have been added to API response for locs/orgs when introduced
Comment 4 Bryan Kearney 2015-05-04 09:40:27 EDT
Created redmine issue http://projects.theforeman.org/issues/10357 from this bug
Comment 5 Bryan Kearney 2015-08-25 14:35:20 EDT
Upstream bug component is Multi Org
Comment 6 Bryan Kearney 2015-12-02 15:07:00 EST
*** Bug 1230873 has been marked as a duplicate of this bug. ***
Comment 7 Bryan Kearney 2016-01-12 04:10:08 EST
Moving to POST since upstream bug http://projects.theforeman.org/issues/10357 has been closed
-------------
Ondřej Pražák
Applied in changeset commit:502feabe1259186625453a9dcc2165ccd0292741.
Comment 12 errata-xmlrpc 2016-07-27 04:50:41 EDT
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

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