Magnum does not support versionless keystone endpoint

Bug #1733883 reported by Michal Nasiadka
24
This bug affects 5 people
Affects Status Importance Assigned to Milestone
Magnum
Confirmed
Undecided
Unassigned

Bug Description

In default installation - kolla project deploys a versionless endpoint in the service catalog:

# openstack catalog show identity
+-----------+--------------------------------------------------------+
| Field | Value |
+-----------+--------------------------------------------------------+
| endpoints | RegionOne |
| | public: https://xxx.xxx.net:5000 |
| | RegionOne |
| | admin: http://xxx.xxx.net:35357 |
| | RegionOne |
| | internal: http://xxx.xxx.net:5000 |
| | |
| id | d5ea252a181b4b2b8e6ecb51ddef4c50 |
| name | keystone |
| type | identity |
+-----------+--------------------------------------------------------+

With this in the catalog, the AUTH_URL is https://xxx.xxx.net:5000 instead of https://xxx.xxx.net:5000/v3

And the script that downloads the certificates fails, due to a problem in token fetch:

# curl -k -s -i -X POST -H "$content_type" -d "$auth_json" $url
HTTP/1.1 404 Not Found
Date: Wed, 22 Nov 2017 14:33:25 GMT
Server: Apache/2.4.18 (Ubuntu)
Vary: X-Auth-Token
X-Distribution: Ubuntu
Content-Length: 146
Content-Type: application/json

{"error": {"message": "(http://xxx.xxx.net:5000/auth/tokens): The resource could not be found.", "code": 404, "title": "Not Found"}}

description: updated
Changed in magnum:
status: New → Confirmed
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.