yahoo-eng-team team mailing list archive

Thread
Date

[Bug 1131215] Re: Bad request response served with 200 status code on metadata delete

To: yahoo-eng-team@xxxxxxxxxxxxxxxxxxx
From: Sean Dague <sean@xxxxxxxxx>
Date: Mon, 30 Mar 2015 15:49:15 -0000
Reply-to: Bug 1131215 <1131215@xxxxxxxxxxxxxxxxxx>
Sender: bounces@xxxxxxxxxxxxx

** Changed in: nova
       Status: Triaged => Won't Fix

** Changed in: nova
     Assignee: Kent Wang (k.wang) => (unassigned)

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

Title:
  Bad request response served with 200 status code on metadata delete

Status in OpenStack Compute (Nova):
  Won't Fix

Bug description:
  The '{ d }' considered as an invalid key by the nova, but the HTTP
  status code is 200, in the response.

  tempest.common.rest_client: INFO: Request: DELETE http://10.34.131.210:8774/v2/50b11029b6d44f41922610b3c7ed7379/servers/999/metadata/{ d }
  tempest.common.rest_client: DEBUG: Request Headers: {'X-Auth-Token': '<Token omitted>'}
  tempest.common.rest_client: INFO: Response Status: 200
  tempest.common.rest_client: DEBUG: Response Body: <head>
  <title>Error response</title>
  </head>
  <body>
  <h1>Error response</h1>
  <p>Error code 400.
  <p>Message: Bad request syntax ('DELETE /v2/50b11029b6d44f41922610b3c7ed7379/servers/999/metadata/{ d } HTTP/1.1').
  <p>Error code explanation: 400 = Bad request syntax or unsupported method.
  </body>

  
  You can modify tempest.tests.compute.servers.test_servers_metadata.test_delete_nonexistant_server_metadata_item in order to reproduce the issue. 

  I also wonder is HTML response format the default ?

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