keystone APIv2.0 unavailable for admin endpoint under apache
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Mirantis OpenStack |
Fix Released
|
Medium
|
MOS Keystone | ||
5.0.x |
Won't Fix
|
Medium
|
MOS Keystone | ||
5.1.x |
Won't Fix
|
Medium
|
MOS Keystone | ||
6.0.x |
Fix Released
|
Medium
|
MOS Keystone | ||
6.1.x |
Fix Released
|
Medium
|
MOS Keystone |
Bug Description
There is a bug https:/
Guys configured keystone + apache by this guide https:/
and their cloud has no V2.0 keystone API on admin endpoint in contrast to public endpoint.
curl http://
{"versions": {"values": [{"status": "stable", "updated": "2013-03-
curl http://
{"versions": {"values": [{"status": "stable", "updated": "2013-03-
But when keystone is started as service (without apache) both v2.0 and v3 API on all endpoints are available.
After debugging the cause was found:
/usr/lib/
@fail_gracefully
def admin_app_
conf = global_conf.copy()
conf.
return wsgi.ComposingR
should be
@fail_gracefully
def admin_app_
controllers
conf = global_conf.copy()
conf.
return wsgi.ComposingR
INFO:
apt-cache policy keystone
keystone:
Installed: 1:2014.
Candidate: 1:2014.
Version table:
*** 1:2014.
500 http://
100 /var/lib/
Changed in mos: | |
status: | Incomplete → Confirmed |
importance: | Undecided → Medium |
assignee: | nobody → MOS Keystone (mos-keystone) |
Changed in mos: | |
status: | Confirmed → Won't Fix |
Changed in mos: | |
status: | Fix Committed → Fix Released |
Please get the output of /api/version, it better identifies MOS version then packages' names.