Bug 917259

Summary: cinder-api mentions application/json requests as Unrecognized requests
Product: Red Hat OpenStack Reporter: Attila Fazekas <afazekas>
Component: python-cinderclientAssignee: Jon Bernard <jobernar>
Status: CLOSED UPSTREAM QA Contact: Giulio Fidente <gfidente>
Severity: low Docs Contact:
Priority: unspecified    
Version: 2.0 (Folsom)CC: abaron, afazekas, apevec, eharney, hateya, jruzicka
Target Milestone: ---   
Target Release: 5.0 (RHEL 7)   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-12-15 16:58:51 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Attila Fazekas 2013-03-02 12:26:58 UTC
python-cinderclient-1.0.1-1.el6ost.noarch
python-cinder-2012.2.3-4.el6ost.noarch

---------
/etc/cinder/cinder.conf:
[DEFAULT]
verbose=True
...
----------

$ cinder --debug list
connect: (10.34.69.149, 35357)
send: 'POST /v2.0/tokens HTTP/1.1\r\nHost: 10.34.69.149:35357\r\nContent-Length: 111\r\ncontent-type: application/json\r\naccept-encoding: gzip, deflate\r\naccept: application/json\r\nuser-agent: python-cinderclient\r\n\r\n'
send: '{"auth": {"tenantName": "admin", "passwordCredentials": {"username": "admin", "password": "92b6f57e64b546bf"}}}'
reply: 'HTTP/1.1 200 OK\r\n'
header: Vary: X-Auth-Token
header: Content-Type: application/json
header: Content-Length: 2067
header: Date: Sat, 02 Mar 2013 12:22:43 GMT
connect: (10.34.69.149, 8776)
send: u'GET /v1/89a38fe6d3194864995ab0872905a65e/volumes/detail HTTP/1.1\r\nHost: 10.34.69.149:8776\r\nx-auth-project-id: admin\r\nx-auth-token: e1b3efe3e5c34576a099ee43ccc053fb\r\naccept-encoding: gzip, deflate\r\naccept: application/json\r\nuser-agent: python-cinderclient\r\n\r\n'
reply: 'HTTP/1.1 200 OK\r\n'
header: X-Compute-Request-Id: req-8c6a5c55-8ff9-4b9a-b5e7-3cdcefb2f067
header: Content-Type: application/json
header: Content-Length: 298
header: Date: Sat, 02 Mar 2013 12:22:43 GMT
+--------------------------------------+-----------+--------------+------+-------------+----------+-------------+
|                  ID                  |   Status  | Display Name | Size | Volume Type | Bootable | Attached to |
+--------------------------------------+-----------+--------------+------+-------------+----------+-------------+
| d75383b3-bb24-49a2-a21a-a13130dfefee | available |     None     |  1   |     None    |          |             |
+--------------------------------------+-----------+--------------+------+-------------+----------+-------------+

New log lines in the /var/log/cinder/api.log:
2013-03-02 12:22:43 INFO cinder.api.openstack.wsgi [req-8c6a5c55-8ff9-4b9a-b5e7-3cdcefb2f067 1d2b871844434bbc99845ed11c3f897b 89a38fe6d3194864995ab0872905a65e] GET http://10.34.69.149:8776/v1/89a38fe6d3194864995ab0872905a65e/volumes/detail
2013-03-02 12:22:43 DEBUG cinder.api.openstack.wsgi [req-8c6a5c55-8ff9-4b9a-b5e7-3cdcefb2f067 1d2b871844434bbc99845ed11c3f897b 89a38fe6d3194864995ab0872905a65e] Unrecognized Content-Type provided in request get_body /usr/lib/python2.6/site-packages/cinder/api/openstack/wsgi.py:696
2013-03-02 12:22:43 AUDIT cinder.api.openstack.volume.volumes [req-8c6a5c55-8ff9-4b9a-b5e7-3cdcefb2f067 1d2b871844434bbc99845ed11c3f897b 89a38fe6d3194864995ab0872905a65e] vol=<cinder.db.sqlalchemy.models.Volume object at 0x26fb890>
2013-03-02 12:22:43 INFO cinder.api.openstack.wsgi [req-8c6a5c55-8ff9-4b9a-b5e7-3cdcefb2f067 1d2b871844434bbc99845ed11c3f897b 89a38fe6d3194864995ab0872905a65e] http://10.34.69.149:8776/v1/89a38fe6d3194864995ab0872905a65e/volumes/detail returned with HTTP 200


application/json content type should not be logged as "Unrecognized Content-Type".

Comment 3 Eric Harney 2013-03-14 20:26:53 UTC
To clarify, it's logged as "Unrecognized" because it is "text/plain" instead of "application/json" -- the GET request for volumes/detail does not seem to send a content-type.

Comment 4 Alan Pevec 2013-03-28 10:51:50 UTC
(In reply to comment #3)
> the GET request for volumes/detail does not seem to send a content-type.

Is that a bug in cinderclient then?

Comment 5 Eric Harney 2013-03-28 13:44:40 UTC
(In reply to comment #4)
> (In reply to comment #3)
> > the GET request for volumes/detail does not seem to send a content-type.
> 
> Is that a bug in cinderclient then?

Hard to say... I guess it would be nice if it did send one, but I'm not sure what the actual requirement/expectation is yet.

Comment 6 Ayal Baron 2013-07-14 06:54:25 UTC
Eric, shouldn't this bug be moved to cinder-client?

Comment 7 Jakub Ruzicka 2013-11-14 17:59:39 UTC
This sounds like a super low priority upstream wishlist bug to me. I suggest reporter file it upstream, link the External Tracker and close UPSTREAM.

Anyway, I'm pretty sure we can move this to 5.0.

Comment 8 Attila Fazekas 2013-11-19 11:00:54 UTC
garbage is garbage.

Added an external bug tracker entry.