Non-API specific 404 exposes traceback
Bug #1089987 reported by
Dolph Mathews
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Identity (keystone) |
Fix Released
|
Medium
|
Dolph Mathews | ||
Folsom |
Fix Released
|
Medium
|
Dolph Mathews |
Bug Description
From the mailing list--
I'm working with Folsom Keystone as packaged in the Ubuntu PPA.
ii keystone 2012.2-
ii python-keystone 2012.2-
In a test setup, I'm seeing Python stack traces on Keystone public API
404s. If I visit <http://
traceback followed by a bit of non-parsing html:
<http://
Is there a configuration directive or a pipeline change that I need to
make to fix this problem? My keystone.conf is very close to vanilla.
<http://
---
Lars Lehtonen
Changed in keystone: | |
status: | New → Confirmed |
importance: | Undecided → Medium |
Changed in keystone: | |
assignee: | Dolph Mathews (dolph) → nobody |
Changed in keystone: | |
assignee: | nobody → Dolph Mathews (dolph) |
Changed in keystone: | |
milestone: | none → grizzly-2 |
status: | Fix Committed → Fix Released |
tags: | removed: in-stable-folsom |
Changed in keystone: | |
milestone: | grizzly-2 → 2013.1 |
To post a comment you must log in.
This is apparently fixed on master, but still reproducible on stable/folsom. On master:
$ curl http:// localhost: 5000/this_ should_ 404
{"error": {"message": "The resource could not be found.", "code": 404, "title": "Not Found"}}
$ curl http:// localhost: 35357/this_ should_ 404
{"error": {"message": "The resource could not be found.", "code": 404, "title": "Not Found"}}