Comment 6 for bug 1435807

This is an actual bug, because even on a deployment that is using the default quota class from the database we'll see the warnings when creating ANY volume unless we manually create the ``volumes_<type-name>``, ``snapshots_<type-name>``, and ``gigabytes_<type-name>`` entries in the ``default`` quota class.

The system should automatically assume that the default value is ``-1``, since the global values (``volumes``, ``snapshots``, and ``gigabytes``), which do exist, will be used on the quota calculations.