openstack team mailing list archive

["Kevin L. Mitchell" <kevin.mitchell@xxxxxxxxxxxxx>]

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.mitchell@xxxxxxxxxxxxx>