Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira ( 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 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 "", 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.
Bug 1216231 - API doc for /api/v2/locations does not mention organizations
Summary: API doc for /api/v2/locations does not mention organizations
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Organizations and Locations
Version: 6.1.0
Hardware: Unspecified
OS: Unspecified
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: Katello QA List
Depends On:
TreeView+ depends on / blocked
Reported: 2015-04-28 20:07 UTC by jaudet
Modified: 2017-01-12 15:30 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2017-01-12 15:30:23 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 10359 0 None None None 2016-04-22 15:00:52 UTC

Description jaudet 2015-04-28 20:07:06 UTC
Description of problem:
The API documentation for /api/v2/locations (at does not make any mention of organizations. This is problematic because it is, in fact, possible to associate a location with an organization by POSTing to /api/v2/locations, and also presumably by PUTting to /api/v2/locations/:id.

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:

Steps to Reproduce:
1.Go to Search for "organization".

Actual results:
No mention of organizations.

Expected results:
Mention of the fact that one can associate a location with zero or more organizations.

Additional info:

Comment 1 RHEL Program Management 2015-04-28 20:13:31 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 3 Bryan Kearney 2015-05-04 13:41:43 UTC
Created redmine issue from this bug

Comment 4 Bryan Kearney 2015-08-25 18:35:16 UTC
Upstream bug component is Multi Org

Comment 5 Bryan Kearney 2016-07-26 15:25:24 UTC
Moving 6.2 bugs out to sat-backlog.

Comment 6 Bryan Kearney 2016-07-26 15:46:17 UTC
Moving 6.2 bugs out to sat-backlog.

Comment 8 Bryan Kearney 2017-01-12 15:30:23 UTC
This is an older bug which has been reported upstream. We are not going to track this bug downstream. When the upstream issue is resolved, the next build will contain the fix. Thank you.

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