When running tempest test (nosetests /tmp/tempest/tempest/tempest/tests/image), the tests are showing new errors when running with glance v2 because they do not add a body to the request. Not sure if change in behavior for glance api v2 is an enhancement or a regression. Anyway, here is the out from the test:
=============
requests.packages.urllib3.connectionpool: INFO: Starting new HTTP connection (1): 127.0.0.1
requests.packages.urllib3.connectionpool: DEBUG: "POST /v2.0/tokens HTTP/1.1" 200 2500
tempest.services.image.json.image_client: INFO: Request: POST http://192.168.4.173:9292/v2/images
tempest.services.image.json.image_client: DEBUG: Request Headers: {'x-image-meta-container_format': 'bare', 'x-image-meta-location': 'http://example.com/someimage.iso', 'X-Auth-Token': u'56110e2098f94b9f8b99bdf9d850069f', 'x-image-meta-is_public': 'True', 'x-image-meta-disk_format': 'raw', 'x-image-meta-name': 'New Remote Image'}
tempest.services.image.json.image_client: INFO: Response Status: 400
tempest.services.image.json.image_client: DEBUG: Response Headers: {'date': 'Wed, 20 Feb 2013 20:52:42 GMT', 'content-length': '47', 'content-type': 'text/plain; charset=UTF-8', 'x-openstack-request-id': 'req-a6f5050c-56b9-48c5-afd2-4722a3be0a37'}
tempest.services.image.json.image_client: DEBUG: Response Body: 400 Bad Request
Body expected in request.
The first thing I notice is that tempest is talking to a v2 endpoint yet sending the v1 headers. Additionally, if the client is sending application/json as the content type, then I do not thing this is a Glance bug. On the other hand, if the client is sending no data, and therefore no content-type, then this is a bug in Glance. Can you provide some more info here?