← Back to team overview

yahoo-eng-team team mailing list archive

[Bug 1800124] [NEW] internal NotFound error can lead to 500 error in modern devstack setup

 

Public bug reported:

I'm using a recent devstack in late October 2018, no special keystone
configuration, it is running under uwsgi and apache2.

If I make a request of the service to a bogus URL:

====
curl -v http://localhost/identity/v3/narf

> GET /identity/v3/narf HTTP/1.1
> Host: localhost
> User-Agent: curl/7.58.0
> Accept: */*
> 
< HTTP/1.1 500 INTERNAL SERVER ERROR
< Date: Fri, 26 Oct 2018 10:08:34 GMT
< Server: Apache/2.4.29 (Ubuntu)
< Content-Type: application/json
< Content-Length: 138
< Vary: X-Auth-Token
< x-openstack-request-id: req-cfafa26b-75a9-4573-9076-61ff9290c6a7
< Connection: close
< 
{"error":{"code":500,"message":"An unexpected error prevented the server from fulfilling your request.","title":"Internal Server Error"}}
====

I stumbled upon this because I was experimenting with pulling the
catalog and requests /v3/catalog instead of /v3/services

Which doesn't seem ideal :)

** Affects: keystone
     Importance: Undecided
         Status: New

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Identity (keystone).
https://bugs.launchpad.net/bugs/1800124

Title:
  internal NotFound error can lead to 500 error in modern devstack setup

Status in OpenStack Identity (keystone):
  New

Bug description:
  I'm using a recent devstack in late October 2018, no special keystone
  configuration, it is running under uwsgi and apache2.

  If I make a request of the service to a bogus URL:

  ====
  curl -v http://localhost/identity/v3/narf

  > GET /identity/v3/narf HTTP/1.1
  > Host: localhost
  > User-Agent: curl/7.58.0
  > Accept: */*
  > 
  < HTTP/1.1 500 INTERNAL SERVER ERROR
  < Date: Fri, 26 Oct 2018 10:08:34 GMT
  < Server: Apache/2.4.29 (Ubuntu)
  < Content-Type: application/json
  < Content-Length: 138
  < Vary: X-Auth-Token
  < x-openstack-request-id: req-cfafa26b-75a9-4573-9076-61ff9290c6a7
  < Connection: close
  < 
  {"error":{"code":500,"message":"An unexpected error prevented the server from fulfilling your request.","title":"Internal Server Error"}}
  ====

  I stumbled upon this because I was experimenting with pulling the
  catalog and requests /v3/catalog instead of /v3/services

  Which doesn't seem ideal :)

To manage notifications about this bug go to:
https://bugs.launchpad.net/keystone/+bug/1800124/+subscriptions


Follow ups