← Back to team overview

yahoo-eng-team team mailing list archive

[Bug 1623517] [NEW] A PUT or POST sent to placement API without a content-type header will result in a 500, should be a 400

 

Public bug reported:

If, by some twist of fate, a user agent send a PUT or POST requests to
the placement API without a content-type header, the service will have
an uncaught KeyError exception raised in webob as it tries to parse the
body of the request. Tests which thought they were testing for this were
not. The webob.dec.wsgify decorator is doing some work before the thing
which the test exercises gets involved. So further tests and guards are
required to avoid the 500.

** Affects: nova
     Importance: Undecided
         Status: New


** Tags: api placement scheduler

** Tags added: api placement scheduler

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

Title:
  A PUT or POST sent to placement API without a content-type header will
  result in a 500, should be a 400

Status in OpenStack Compute (nova):
  New

Bug description:
  If, by some twist of fate, a user agent send a PUT or POST requests to
  the placement API without a content-type header, the service will have
  an uncaught KeyError exception raised in webob as it tries to parse
  the body of the request. Tests which thought they were testing for
  this were not. The webob.dec.wsgify decorator is doing some work
  before the thing which the test exercises gets involved. So further
  tests and guards are required to avoid the 500.

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


Follow ups