Re: [Openstack] Grizzly Dashboard Quota Problem...
Hey Thiago! Did you open a bug for this issue? If so let me know (I'm maurosr at the irc channels), it seems we need to deal with this in conductor. If you're going to open the bug now, please don't forget to add the conductor log. Thanks, -- Mauro S M Rodrigues Software Engineer IBM LTC Brazil On 03/15/2013 08:57 PM, Martinx - ? wrote: Hi! I don't know if it is related to this issue but, when I Terminate an Instance, nova-conductor.log shows: 2013-03-15 20:56:33.739 ERROR nova.quota [req-558f180c-4092-4dad-9be0-04b105e6a51b 773fad6638fe4def95dd996db7af5161 7428cb7265d04ff398202b45f84d96bf] Failed to commit reservations [u'73a2da17-7b5a-4913-87f2-33bf47b7ab02', u'd2e4334a-679d-4664-bdc9-abff1247c89c', u'b284d408-2788-4fad-b191-9fc6f857cdee'] 2013-03-15 20:56:33.739 6218 TRACE nova.quota Traceback (most recent call last): 2013-03-15 20:56:33.739 6218 TRACE nova.quota File /usr/lib/python2.7/dist-packages/nova/quota.py, line 982, in commit 2013-03-15 20:56:33.739 6218 TRACE nova.quota self._driver.commit(context, reservations, project_id=project_id) 2013-03-15 20:56:33.739 6218 TRACE nova.quota File /usr/lib/python2.7/dist-packages/nova/quota.py, line 370, in commit 2013-03-15 20:56:33.739 6218 TRACE nova.quota db.reservation_commit(context, reservations, project_id=project_id) 2013-03-15 20:56:33.739 6218 TRACE nova.quota File /usr/lib/python2.7/dist-packages/nova/db/api.py, line 972, in reservation_commit 2013-03-15 20:56:33.739 6218 TRACE nova.quota project_id=project_id) 2013-03-15 20:56:33.739 6218 TRACE nova.quota File /usr/lib/python2.7/dist-packages/nova/db/sqlalchemy/api.py, line 112, in wrapper 2013-03-15 20:56:33.739 6218 TRACE nova.quota return f(*args, **kwargs) 2013-03-15 20:56:33.739 6218 TRACE nova.quota File /usr/lib/python2.7/dist-packages/nova/db/sqlalchemy/api.py, line 2681, in reservation_commit 2013-03-15 20:56:33.739 6218 TRACE nova.quota usage = usages[reservation.resource] 2013-03-15 20:56:33.739 6218 TRACE nova.quota KeyError: u'instances' 2013-03-15 20:56:33.739 6218 TRACE nova.quota Tks, Thiago On 15 March 2013 20:37, Martinx - ? thiagocmarti...@gmail.com mailto:thiagocmarti...@gmail.com wrote: Hi! Finally I have my Grizzly G3 + RC1 working! But, when I tried to setup the Project quotas, an error appear on the Dashboard and at Apache error.log. The error appear even when creating a Project, with default quota settings... Dashboard message: Error: Unable to set project quotas. error.log: [Fri Mar 15 23:35:57 2013] [error] \x1b[31;1mRecoverable error: Bad key(s) gigabytes,volumes in quota_set (HTTP 400) (Request-ID: req-555844dc-3cdc-4a33-a7e8-c1836b8f)\x1b[0m Is this a know BUG? Can I do something about it? Thanks! Thiago ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] Grizzly Dashboard Quota Problem...
Hello Mauro! I'm reinstalling everything (Grizzly from PPA) from scratch again, if I hit the BUG one more time, I'll let you guys know. Best Regards, Thiago On 18 March 2013 13:11, Mauro Rodrigues maur...@linux.vnet.ibm.com wrote: Hey Thiago! Did you open a bug for this issue? If so let me know (I'm maurosr at the irc channels), it seems we need to deal with this in conductor. If you're going to open the bug now, please don't forget to add the conductor log. Thanks, -- Mauro S M Rodrigues Software Engineer IBM LTC Brazil On 03/15/2013 08:57 PM, Martinx - ジェームズ wrote: Hi! I don't know if it is related to this issue but, when I Terminate an Instance, nova-conductor.log shows: 2013-03-15 20:56:33.739 ERROR nova.quota [req-558f180c-4092-4dad-9be0-04b105e6a51b 773fad6638fe4def95dd996db7af5161 7428cb7265d04ff398202b45f84d96bf] Failed to commit reservations [u'73a2da17-7b5a-4913-87f2-33bf47b7ab02', u'd2e4334a-679d-4664-bdc9-abff1247c89c', u'b284d408-2788-4fad-b191-9fc6f857cdee'] 2013-03-15 20:56:33.739 6218 TRACE nova.quota Traceback (most recent call last): 2013-03-15 20:56:33.739 6218 TRACE nova.quota File /usr/lib/python2.7/dist-packages/nova/quota.py, line 982, in commit 2013-03-15 20:56:33.739 6218 TRACE nova.quota self._driver.commit(context, reservations, project_id=project_id) 2013-03-15 20:56:33.739 6218 TRACE nova.quota File /usr/lib/python2.7/dist-packages/nova/quota.py, line 370, in commit 2013-03-15 20:56:33.739 6218 TRACE nova.quota db.reservation_commit(context, reservations, project_id=project_id) 2013-03-15 20:56:33.739 6218 TRACE nova.quota File /usr/lib/python2.7/dist-packages/nova/db/api.py, line 972, in reservation_commit 2013-03-15 20:56:33.739 6218 TRACE nova.quota project_id=project_id) 2013-03-15 20:56:33.739 6218 TRACE nova.quota File /usr/lib/python2.7/dist-packages/nova/db/sqlalchemy/api.py, line 112, in wrapper 2013-03-15 20:56:33.739 6218 TRACE nova.quota return f(*args, **kwargs) 2013-03-15 20:56:33.739 6218 TRACE nova.quota File /usr/lib/python2.7/dist-packages/nova/db/sqlalchemy/api.py, line 2681, in reservation_commit 2013-03-15 20:56:33.739 6218 TRACE nova.quota usage = usages[reservation.resource] 2013-03-15 20:56:33.739 6218 TRACE nova.quota KeyError: u'instances' 2013-03-15 20:56:33.739 6218 TRACE nova.quota Tks, Thiago On 15 March 2013 20:37, Martinx - ジェームズ thiagocmarti...@gmail.com wrote: Hi! Finally I have my Grizzly G3 + RC1 working! But, when I tried to setup the Project quotas, an error appear on the Dashboard and at Apache error.log. The error appear even when creating a Project, with default quota settings... Dashboard message: Error: Unable to set project quotas. error.log: [Fri Mar 15 23:35:57 2013] [error] \x1b[31;1mRecoverable error: Bad key(s) gigabytes,volumes in quota_set (HTTP 400) (Request-ID: req-555844dc-3cdc-4a33-a7e8-c1836b8f)\x1b[0m Is this a know BUG? Can I do something about it? Thanks! Thiago ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] Grizzly Dashboard Quota Problem...
On Mon, 2013-03-18 at 14:57 -0300, Martinx - ジェームズ wrote: I'm reinstalling everything (Grizzly from PPA) from scratch again, if I hit the BUG one more time, I'll let you guys know. I believe the quota settings error is a bug in nova, rather than in horizon or novaclient. The problem is that, recently, a change went in that causes nova to reject quota update requests that have unrecognized quotas. The problem is that older versions of nova had two quota resources (gigabytes and volumes) that have been removed in Grizzly, because of the nova/cinder split. Thus, all clients that operate against pre-Grizzly nova will fail to work with Grizzly nova…and it is also the case that novaclient and probably horizon have not been updated to remove those two quota resources. The correct fix will probably be to revert the nova merge that causes this HttpBadRequest to be raised, and to subsequently apply the IETF mantra: Be liberal in what you accept and conservative in what you send. -- Kevin L. Mitchell kevin.mitch...@rackspace.com ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] Grizzly Dashboard Quota Problem...
We landed a fix in Horizon yesterday ( tracked in https://bugs.launchpad.net/horizon/+bug/1155876 ) that addresses this problem for the Grizzly RC. Nova should have followed a proper deprecation path here and accepted the parameters in this release and reject them (if they really must) in Havana. Stripping them out in novaclient and logging a deprecation warning would also have been an acceptable solution. In general, any backwards-incompatible change in an API needs to be versioned and/or properly deprecated. - Gabriel -Original Message- From: openstack-bounces+gabriel.hurley=nebula@lists.launchpad.net [mailto:openstack- bounces+gabriel.hurley=nebula@lists.launchpad.net] On Behalf Of Kevin L. Mitchell Sent: Monday, March 18, 2013 11:11 AM To: openstack@lists.launchpad.net Subject: Re: [Openstack] Grizzly Dashboard Quota Problem... On Mon, 2013-03-18 at 14:57 -0300, Martinx - ジェームズ wrote: I'm reinstalling everything (Grizzly from PPA) from scratch again, if I hit the BUG one more time, I'll let you guys know. I believe the quota settings error is a bug in nova, rather than in horizon or novaclient. The problem is that, recently, a change went in that causes nova to reject quota update requests that have unrecognized quotas. The problem is that older versions of nova had two quota resources (gigabytes and volumes) that have been removed in Grizzly, because of the nova/cinder split. Thus, all clients that operate against pre-Grizzly nova will fail to work with Grizzly nova…and it is also the case that novaclient and probably horizon have not been updated to remove those two quota resources. The correct fix will probably be to revert the nova merge that causes this HttpBadRequest to be raised, and to subsequently apply the IETF mantra: Be liberal in what you accept and conservative in what you send. -- Kevin L. Mitchell kevin.mitch...@rackspace.com ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
[Openstack] Grizzly Dashboard Quota Problem...
Hi! Finally I have my Grizzly G3 + RC1 working! But, when I tried to setup the Project quotas, an error appear on the Dashboard and at Apache error.log. The error appear even when creating a Project, with default quota settings... Dashboard message: Error: Unable to set project quotas. error.log: [Fri Mar 15 23:35:57 2013] [error] \x1b[31;1mRecoverable error: Bad key(s) gigabytes,volumes in quota_set (HTTP 400) (Request-ID: req-555844dc-3cdc-4a33-a7e8-c1836b8f)\x1b[0m Is this a know BUG? Can I do something about it? Thanks! Thiago ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] Grizzly Dashboard Quota Problem...
Hi! I don't know if it is related to this issue but, when I Terminate an Instance, nova-conductor.log shows: 2013-03-15 20:56:33.739 ERROR nova.quota [req-558f180c-4092-4dad-9be0-04b105e6a51b 773fad6638fe4def95dd996db7af5161 7428cb7265d04ff398202b45f84d96bf] Failed to commit reservations [u'73a2da17-7b5a-4913-87f2-33bf47b7ab02', u'd2e4334a-679d-4664-bdc9-abff1247c89c', u'b284d408-2788-4fad-b191-9fc6f857cdee'] 2013-03-15 20:56:33.739 6218 TRACE nova.quota Traceback (most recent call last): 2013-03-15 20:56:33.739 6218 TRACE nova.quota File /usr/lib/python2.7/dist-packages/nova/quota.py, line 982, in commit 2013-03-15 20:56:33.739 6218 TRACE nova.quota self._driver.commit(context, reservations, project_id=project_id) 2013-03-15 20:56:33.739 6218 TRACE nova.quota File /usr/lib/python2.7/dist-packages/nova/quota.py, line 370, in commit 2013-03-15 20:56:33.739 6218 TRACE nova.quota db.reservation_commit(context, reservations, project_id=project_id) 2013-03-15 20:56:33.739 6218 TRACE nova.quota File /usr/lib/python2.7/dist-packages/nova/db/api.py, line 972, in reservation_commit 2013-03-15 20:56:33.739 6218 TRACE nova.quota project_id=project_id) 2013-03-15 20:56:33.739 6218 TRACE nova.quota File /usr/lib/python2.7/dist-packages/nova/db/sqlalchemy/api.py, line 112, in wrapper 2013-03-15 20:56:33.739 6218 TRACE nova.quota return f(*args, **kwargs) 2013-03-15 20:56:33.739 6218 TRACE nova.quota File /usr/lib/python2.7/dist-packages/nova/db/sqlalchemy/api.py, line 2681, in reservation_commit 2013-03-15 20:56:33.739 6218 TRACE nova.quota usage = usages[reservation.resource] 2013-03-15 20:56:33.739 6218 TRACE nova.quota KeyError: u'instances' 2013-03-15 20:56:33.739 6218 TRACE nova.quota Tks, Thiago On 15 March 2013 20:37, Martinx - ジェームズ thiagocmarti...@gmail.com wrote: Hi! Finally I have my Grizzly G3 + RC1 working! But, when I tried to setup the Project quotas, an error appear on the Dashboard and at Apache error.log. The error appear even when creating a Project, with default quota settings... Dashboard message: Error: Unable to set project quotas. error.log: [Fri Mar 15 23:35:57 2013] [error] \x1b[31;1mRecoverable error: Bad key(s) gigabytes,volumes in quota_set (HTTP 400) (Request-ID: req-555844dc-3cdc-4a33-a7e8-c1836b8f)\x1b[0m Is this a know BUG? Can I do something about it? Thanks! Thiago ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] Grizzly Dashboard Quota Problem...
Hi Thiago, I haven't seen that before. Can you file a bug for it? https://bugs.launchpad.net/horizon/+filebug It may be something to do with a missing volume service, but that service should be optional. Cheers, Kieran On 16 March 2013 10:37, Martinx - ジェームズ thiagocmarti...@gmail.com wrote: Hi! Finally I have my Grizzly G3 + RC1 working! But, when I tried to setup the Project quotas, an error appear on the Dashboard and at Apache error.log. The error appear even when creating a Project, with default quota settings... Dashboard message: Error: Unable to set project quotas. error.log: [Fri Mar 15 23:35:57 2013] [error] \x1b[31;1mRecoverable error: Bad key(s) gigabytes,volumes in quota_set (HTTP 400) (Request-ID: req-555844dc-3cdc-4a33-a7e8-c1836b8f)\x1b[0m Is this a know BUG? Can I do something about it? Thanks! Thiago ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
