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.

Bug 1292275

Summary: /api/v2/locations does not return parameters
Product: Red Hat Satellite Reporter: Andrew Schofield <andrew.schofield>
Component: Organizations and LocationsAssignee: Shlomi Zadok <szadok>
Status: CLOSED ERRATA QA Contact: Katello QA List <katello-qa-list>
Severity: high Docs Contact:
Priority: high    
Version: 6.1.5CC: bbuckingham, jcallaha, kabbott, sthirugn
Target Milestone: UnspecifiedKeywords: Triaged
Target Release: Unused   
Hardware: All   
OS: Linux   
URL: http://projects.theforeman.org/issues/13386
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-07-27 09:00:31 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Andrew Schofield 2015-12-16 21:31:51 UTC 
Description of problem:

GET /api/v2/locations/<location> does not return the parameters

Version-Release number of selected component (if applicable):
Satellite 6.1.5

How reproducible:
Repeatable.

Steps to Reproduce:
1. Create a location and in this location assign a parameter.
2. GET /api/v2/locations/<location>
3. Note the output does not contain the parameter:


Actual results:
"parameters": [
    {

    }
  ],


Expected results:
parameters to be populated with the parameters from step 1 above.

Additional info:

This is also the same issue for hammer:

# hammer location info --name <location>

Parameters:
     =>
Organizations:
Comment 2 Brad Buckingham 2016-01-26 17:43:39 UTC 
Created redmine issue http://projects.theforeman.org/issues/13386 from this bug
Comment 3 Bryan Kearney 2016-01-26 19:12:42 UTC 
Upstream bug component is Provisioning
Comment 4 Bryan Kearney 2016-01-27 09:13:30 UTC 
Upstream bug component is Multi Org
Comment 5 Bryan Kearney 2016-02-03 15:12:30 UTC 
Upstream bug assigned to szadok
Comment 6 Bryan Kearney 2016-02-09 11:12:21 UTC 
Moving to POST since upstream bug http://projects.theforeman.org/issues/13386 has been closed
-------------
Shlomi Zadok
Applied in changeset commit:019a239c93421bb94b57e5683e304a61b35117d7.
Comment 8 jcallaha 2016-03-24 20:44:03 UTC 
Verified in Satellite 6.2 beta Snap 5.1.

{
  "total": 1,
  "subtotal": 1,
  "page": 1,
  "per_page": 20,
  "search": null,
  "sort": {
    "by": null,
    "order": null
  },
  "results": [
    {
      "ancestry": null,
      "parent_id": null,
      "parent_name": null,
      "created_at": "2016-03-11 16:29:11 UTC",
      "updated_at": "2016-03-11 16:29:11 UTC",
      "id": 2,
      "name": "Default Location",
      "title": "Default Location",
      "description": null
    }
  ]
}
Comment 11 errata-xmlrpc 2016-07-27 09:00:31 UTC 
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