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 documentation for /api/v2/locations (at https://sat.example.com/apidoc/v2/locations.html) does not make any mention of parent locations. This is problematic because it is, in fact, possible to associate a location with a parent 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:
100%

Steps to Reproduce:
1.Go to https://sat.example.com/apidoc/v2/locations.html. Search for "parent".

Actual results:
No mention of parents.

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

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.

it does mention parents, but it's not obvious. The attribute 'ancestry' is the parent. If there is only one parent, it's the id such as {ancestry: "3"}. If it is a "grandchild", then it would look like this {ancestry: "3/41"} when 41 is the direct parent id and 3 is the parent's parent id.

Created redmine issue http://projects.theforeman.org/issues/10358 from this bug

Upstream bug component is Multi Org

Moving 6.2 bugs out to sat-backlog.

Moving 6.2 bugs out to sat-backlog.

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.