← Back to team overview

yahoo-eng-team team mailing list archive

  1. yahoo-eng-team team
  2. Mailing list archive
  3. Message #16738

[Bug 1334297] Re: Strange response from os-server-groups with bad parameter

  Thread Previous • Date Previous • • Thread Next 
So in the end I don't think this is a Nova bug. The first line of the
request to the Nova API server looks like this:

DELETE /v2/f9cea8784d7245e5a8022a259bb92d90/os-server-
groups/{u'policies': [u'affinity'], u'name': u'server-group-1646113520',
u'id': u'b5316a4a-f6eb-4a7f-8b24-028b799bf6a9', u'members': [],
u'metadata': {}} HTTP/1.1

Which is not a valid header. It is so badly formatted that I believe a
reasonable parser implementation could not necessarily know that the
client is requesting a response in HTTP/1.1 format as the uri is so
corrupt. Looking from the end it can be clearly seen, but the request is
definitely corrupt. BaseHTTPServer by default responds in HTTP/0.9
protocol if its not sure.

So it does return a 400, but in HTTP/0.9 protocol:

<title>Error response</title>
</head>
<body>
<h1>Error response</h1>
<p>Error code 400.
<p>Message: Bad request syntax ("DELETE /v2/f9cea8784d7245e5a8022a259bb92d90/os-server-groups/{u'policies': [u'affinity'], u'name': u'server-group-1646113520', u'id': u'b5316a4a-f6eb-4a7f-8b24-028b799bf6a9', u'members': [], u'metadata': {}} HTTP/1.1").
<p>Error code explanation: 400 = Bad request syntax or unsupported method.
</body>

httplib2 on the tempest side  made the request in HTTP/1.1 protocol, but
does not appear to try to parse it in HTTP/0.9 format if it doesn't get
an HTTP/1.1 header. According to RFC 1945 it should be able to do so. So
technically its a tempest bug. Not sure if its worth fixing though....


** Also affects: tempest
   Importance: Undecided
       Status: New

** Changed in: tempest
   Importance: Undecided => Low

** 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/1334297

Title:
  Strange response from os-server-groups with bad parameter

Status in OpenStack Compute (Nova):
  Invalid
Status in Tempest:
  New

Bug description:
  There was a bug in tempest that caused a call to DELETE os-server-
  groups with a bad id. Here is the call from the tempest log:

  2014-06-25 12:07:03.162 25653 INFO tempest.common.rest_client [-]
  Request (ServerGroupTestJSON:tearDownClass): 200 DELETE
  http://127.0.0.1:8774/v2/2bc18b72010d455a9db7cbc583e1dcfc/os-server-
  groups/{u'policies': [u'affinity'], u'name': u'server-
  group-1944635656', u'id': u'7c6a13c1-6d8b-4314-9d16-4eb6418a2170',
  u'members': [], u'metadata': {}} 0.001s

  Normally DELETE will return 204 and in this case I would have expected
  400. But the call returns 200. What can be seen in the nova log seems
  to indicate 400 but that is not what is actually getting sent back:

  127.0.0.1 - - [25/Jun/2014 12:07:03] code 400, message Bad request syntax ("DELETE /v2/2bc18b72010d455a9db7cbc583e1dcfc/os-server-groups/{u'policies': [u'affinity'], u'name': u'server-group-1944635656', u'id': u'7c6a13c1-6d8b-4314-9d16-4eb6418a2170', u'members': [], u'metadata': {}} HTTP/1.1")
  127.0.0.1 - - [25/Jun/2014 12:07:03] "DELETE /v2/2bc18b72010d455a9db7cbc583e1dcfc/os-server-groups/{u'policies': [u'affinity'], u'name': u'server-group-1944635656', u'id': u'7c6a13c1-6d8b-4314-9d16-4eb6418a2170', u'members': [], u'metadata': {}} HTTP/1.1" 400 -
  127.0.0.1 - - [25/Jun/2014 12:07:03] code 400, message Bad request syntax ("DELETE /v2/2bc18b72010d455a9db7cbc583e1dcfc/os-server-groups/{u'policies': [u'affinity'], u'name': u'server-group-1366165944', u'id': u'd361d100-fc59-4393-b61b-30a2d4b27b6e', u'members': [], u'metadata': {}} HTTP/1.1")
  127.0.0.1 - - [25/Jun/2014 12:07:03] "DELETE /v2/2bc18b72010d455a9db7cbc583e1dcfc/os-server-groups/{u'policies': [u'affinity'], u'name': u'server-group-1366165944', u'id': u'd361d100-fc59-4393-b61b-30a2d4b27b6e', u'members': [], u'metadata': {}} HTTP/1.1" 400 -
  127.0.0.1 - - [25/Jun/2014 12:07:03] code 400, message Bad request syntax ("DELETE /v2/2bc18b72010d455a9db7cbc583e1dcfc/os-server-groups/{u'policies': [u'affinity'], u'name': u'server-group-1366165944', u'id': u'9f8574d7-78b9-4926-98ea-61f2da971478', u'members': [], u'metadata': {}} HTTP/1.1")
  127.0.0.1 - - [25/Jun/2014 12:07:03] "DELETE /v2/2bc18b72010d455a9db7cbc583e1dcfc/os-server-groups/{u'policies': [u'affinity'], u'name': u'server-group-1366165944', u'id': u'9f8574d7-78b9-4926-98ea-61f2da971478', u'members': [], u'metadata': {}} HTTP/1.1" 400 -
  127.0.0.1 - - [25/Jun/2014 12:07:03] code 400, message Bad request syntax ("DELETE /v2/2bc18b72010d455a9db7cbc583e1dcfc/os-server-groups/{u'policies': [u'affinity'], u'name': u'server-group-2072440191', u'id': u'01342594-9661-47fb-8816-e816ad2cae37', u'members': [], u'metadata': {}} HTTP/1.1")
  127.0.0.1 - - [25/Jun/2014 12:07:03] "DELETE /v2/2bc18b72010d455a9db7cbc583e1dcfc/os-server-groups/{u'policies': [u'affinity'], u'name': u'server-group-2072440191', u'id': u'01342594-9661-47fb-8816-e816ad2cae37', u'members': [], u'metadata': {}} HTTP/1.1" 400 -
  127.0.0.1 - - [25/Jun/2014 12:07:03] code 400, message Bad request syntax ("DELETE /v2/2bc18b72010d455a9db7cbc583e1dcfc/os-server-groups/{u'policies': [u'anti-affinity'], u'name': u'server-group-684827235', u'id': u'53c45946-5a0b-451e-bf24-790b1db89963', u'members': [], u'metadata': {}} HTTP/1.1")
  127.0.0.1 - - [25/Jun/2014 12:07:03] "DELETE /v2/2bc18b72010d455a9db7cbc583e1dcfc/os-server-groups/{u'policies': [u'anti-affinity'], u'name': u'server-group-684827235', u'id': u'53c45946-5a0b-451e-bf24-790b1db89963', u'members': [], u'metadata': {}} HTTP/1.1" 400 -

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

References

  Thread Previous • Date Previous • • Thread Next