yahoo-eng-team team mailing list archive

[Sujitha <sujitha.neti@xxxxxxxxx>]

** Changed in: nova
       Status: Confirmed => Invalid

-- 
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/1235220

Title:
  Nova API returns unicode Location Header

Status in OpenStack Compute (nova):
  Invalid
Status in Ubuntu:
  Confirmed

Bug description:
  The Nova Compute API returns a series of headers as a result of create
  operation. The location header is being returned as a unicode value
  which is not compliant with the RFC for HTTP.

  I haven't figured out yet whether this is a global thing or specific
  to something more localised.

  While not a problem when running with nova-api services directly the
  problem manifests itself if a user was to front the API with something
  that requires rfc compliant headers to be returned, such as Apache.

  Eg execute: nova image-create 69136d40-8de0-4a63-b03a-16543d390c8e
  test-snap-20131004-10

  Response:
  ERROR: <attribute 'message' of 'exceptions.BaseException' objects> (HTTP 500)

  Apache's error log shows:
  [Fri Oct 04 14:08:42 2013] [error] [client 192.168.4.63] mod_wsgi (pid=20280): Exception occurred processing WSGI script '/etc/apache2/wsgi/nova-api-os-compute'.
  [Fri Oct 04 14:08:42 2013] [error] [client 192.168.4.63] TypeError: expected byte string object for header value, value of type unicode found

  The actual image-create ends up being successful, even though the
  client receives a HTTP 500 response.

  Environment: Openstack Grizzly on Ubuntu with package level 2013.1.3

  While this is the same result as
  https://bugs.launchpad.net/nova/+bug/938114 It appears to me that this
  is more localised.

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