Hide Forgot
Description of problem: [root@puma31 ~(keystone_user)]# cinder rate-limits [root@puma31 ~(keystone_user)]# cinder absolute-limits +-------------------------+-------+ | Name | Value | +-------------------------+-------+ | maxTotalVolumeGigabytes | 1000 | | maxTotalVolumes | 10 | +-------------------------+-------+ [root@puma31 ~(keystone_user)]# this affects nova too, relevant DEBUG lines from the api.log: 2013-12-03 18:41:27.181 17684 INFO cinder.api.openstack.wsgi [req-0994a57b-4043-4ace-91e4-c2760574beb1 24bd954b1a3b43719a450ec1f0ecc216 ef7e87266d994ab9b2c963cc68e9a4c7] GET http://10.35.160. 73:8776/v1/ef7e87266d994ab9b2c963cc68e9a4c7/limits 2013-12-03 18:41:27.181 17684 DEBUG cinder.api.openstack.wsgi [req-0994a57b-4043-4ace-91e4-c2760574beb1 24bd954b1a3b43719a450ec1f0ecc216 ef7e87266d994ab9b2c963cc68e9a4c7] Unrecognized Content -Type provided in request get_body /usr/lib/python2.6/site-packages/cinder/api/openstack/wsgi.py:718 2013-12-03 18:41:27.182 17684 DEBUG cinder.openstack.common.lockutils [req-0994a57b-4043-4ace-91e4-c2760574beb1 24bd954b1a3b43719a450ec1f0ecc216 ef7e87266d994ab9b2c963cc68e9a4c7] Got semaphor e "dbapi_backend" for method "__get_backend"... inner /usr/lib/python2.6/site-packages/cinder/openstack/common/lockutils.py:191 Version-Release number of selected component (if applicable): openstack-cinder-2013.2-3.el6ost.noarch Steps to Reproduce: 1. run "cinder rate-limits" against some working environment
Jon, any update on this one?
I have reproduced this on my machine as described. Upstream does not seem to suffer from this issue (devstack, master branch). I'll work on figuring out what's going on.
The bug is in the cinder client. Interestingly, 1.0.7 is the version reported by the rpm - and it exhibits the bug. But 1.0.7 installed from the source tree does not exhibit this bug. Are there any internal patches added on top of the upstream release? Also, can you tell me what is the version string reported from 'cinder --version' ?
I changed the component to python-cinderclient. If you use the '--debug' option on the command line, you can see that cinder is returning the correct results but the client is not displaying them correctly. Simplying applying the two includes patches to the 1.0.7 source doesn't seem to cause the bug, so I need to dig a bit more.
This appears to be an incorrect version requirement on 'python-prettytable' We have 0.6.1, but we (python-cinderclient) require at least 0.7. So we either need python-prettytable>=0.7 or we must go to an earlier version of python-cinderclient.
I did not set any limits but we are getting an output: [root@orange-vdsf ~(keystone_admin)]# cinder rate-limits +------+-----+-------+--------+------+----------------+ | Verb | URI | Value | Remain | Unit | Next_Available | +------+-----+-------+--------+------+----------------+ +------+-----+-------+--------+------+----------------+ [root@orange-vdsf ~(keystone_admin)]# moving to verified on [root@orange-vdsf ~(keystone_admin)]# rpm -qa |grep cinder openstack-cinder-2013.2.2-1.el6ost.noarch python-cinderclient-1.0.7-2.el6ost.noarch python-cinder-2013.2.2-1.el6ost.noarch
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHBA-2014-0213.html