Comment 2 for bug 1233763

I have investigated this further and discovered that this appears to be happening on systems where no default quota class has been setup on the system. I was able to avoid the error message by doing "cinder quota-class-update default --volume 10 --snapshots 10 --gigabytes 1000"

Given that quota_class_get_default is set to true by default, it seems we should be setting up default values in the database to go with the configuration setting. This seems like something we should do as part of the database configuration perhaps?