Bug 1485424

Summary: Invalid "href" value in "versions" when API version is specified
Product: Red Hat CloudForms Management Engine Reporter: Martin Kourim <mkourim>
Component: APIAssignee: Jillian Tullo <jtullo>
Status: CLOSED ERRATA QA Contact: Martin Kourim <mkourim>
Severity: medium Docs Contact:
Priority: medium    
Version: 5.8.0CC: dajohnso, jhardy, jtullo, mkourim, obarenbo, simaishi
Target Milestone: GA   
Target Release: 5.9.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: api:rest
Fixed In Version: 5.9.0.2 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-03-01 13:16:22 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 Martin Kourim 2017-08-25 16:14:16 UTC
Description of problem:
Invalid "href" value in "versions" when API version is specified:

"versions": [
        {
            "name": "2.4.0",
            "href": "https://10.8.196.108/api/v2.4.0/v2.4.0"
        }
    ],

The "https://10.8.196.108/api/v2.4.0/v2.4.0" doesn't exist.


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


How reproducible:
very


Steps to Reproduce:
1. GET /api/v2.4.0/


Expected results:
"href": "https://10.8.196.108/api/v2.4.0

Comment 2 Dave Johnson 2017-09-18 16:58:28 UTC
Martin, is there any impact to automation from this?  If so, please add PrioBumpQA keyword above.

Comment 3 Jillian Tullo 2017-09-28 19:35:39 UTC
PR: https://github.com/ManageIQ/manageiq-api/pull/87

Comment 4 Martin Kourim 2017-10-17 20:09:03 UTC
Verified that the "href" value is valid when API version is specified
GET /api/v3.0.0-pre

Comment 7 errata-xmlrpc 2018-03-01 13:16:22 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/RHSA-2018:0380