Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1361114 - Can't access foreman location parameters
Can't access foreman location parameters
Status: CLOSED ERRATA
Product: Red Hat Satellite 6
Classification: Red Hat
Component: Organizations and Locations (Show other bugs)
6.1.0
Unspecified Unspecified
high Severity high (vote)
: 6.1.10
: Unused
Assigned To: satellite6-bugs
http://projects.theforeman.org/issues...
: Triaged, ZStream
Depends On: 1221710
Blocks: 1256461
  Show dependency treegraph
 
Reported: 2016-07-28 07:15 EDT by Tomas Strachota
Modified: 2017-02-23 14:37 EST (History)
14 users (show)

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 1221710
Environment:
Last Closed: 2016-09-27 05:03: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
Red Hat Product Errata RHBA-2016:1938 normal SHIPPED_LIVE Satellite 6.1.10 bug fix update 2016-09-27 08:56:10 EDT

  None (edit)
Comment 1 Tomas Strachota 2016-07-28 07:17:23 EDT
Cloning for 6.1.z
Comment 3 jcallaha 2016-09-21 16:48:37 EDT
Verified in Satellite 6.1.10 Snap 1.1. 
You can now see the parameters for a location when using the parameters path. However, you cannot view the parameters when visiting the base path. As this issue does not stop us from viewing the parameters, I will not fail this bug, instead a new one will be filed.

GET https://rhsm-qe-1.rhq.lab.eng.bos.redhat.com/api/v2/locations/3/parameters/
{
  "total": 2,
  "subtotal": 2,
  "page": 1,
  "per_page": 20,
  "search": null,
  "sort": {
    "by": null,
    "order": null
  },
  "results": [
    {
      "id": 3,
      "name": "param1",
      "value": "first test parameter",
      "priority": null,
      "created_at": "2016-09-21T20:38:04Z",
      "updated_at": "2016-09-21T20:38:04Z"
    },
    {
      "id": 4,
      "name": "param2",
      "value": "second test parameter",
      "priority": null,
      "created_at": "2016-09-21T20:38:04Z",
      "updated_at": "2016-09-21T20:38:04Z"
    }
  ]
}



GET https://rhsm-qe-1.rhq.lab.eng.bos.redhat.com/api/v2/locations/3
{
  "id": 3,
  "name": "Brand New Location",
  "title": "Default Location/Brand New Location",
  "created_at": "2016-09-20T19:31:12Z",
  "updated_at": "2016-09-21T20:38:34Z",
  "select_all_types": [
    "ConfigTemplate",
    "Hostgroup"
  ],
  "description": "",
  "parameters": [
    {},
    {}
  ],
  "users": [],
  "smart_proxies": [],
  "subnets": [],
  "compute_resources": [],
  "media": [],
  "config_templates": [],
  "domains": [],
  "environments": [],
  "hostgroups": [],
  "organizations": []
}
Comment 5 errata-xmlrpc 2016-09-27 05:03: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:1938

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