Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=1566630

Description of problem:

We create parameters in Locations using API. An example of the location XYZ

In Satellite 6.2, we can list the parameters with the URL:

https://satellite62.example.com/api/v2/locations/XYZ/parameters/

However, in Satellite 6.3, we don't have the same results, we get the error:
"Location with id XYZ not found"

We have to use the ID (id of XYZ is 10) instead to get correct parameters:

https://satellite63.example.com/api/v2/locations/api/v2/locations/10/parameters/

Version-Release number of selected component (if applicable):
satellite 6.3.0

How reproducible:

100% reproducible by URL mentioned and step mentioned in the description.

API call is same in the APIDOC of satellite 6.2 and satellite 6.3 for listing out parameters associated with a location.

"GET /api/locations/:location_id/parameters"

however, in 6.2 somehow it was resolving the name of the location to its id whereas in 6.3 it is not doing the same thing, might be there is some change in code.

Actual results:

while listing the parameters with the URL:

https://satellite62.example.com/api/v2/locations/XYZ/parameters/

in Satellite 6.3, we get the error:
"Location with id XYZ not found" -->> XYZ is the location name

Expected results:

while listing the parameters with the URL:

https://satellite62.example.com/api/v2/locations/XYZ/parameters/

in Satellite 6.3, we should get parameters listed for XYZ location i.e: hostname should resolve id automatically as it used to do in satellite 6.2.