Comment 1 for bug 1200709

So what's happening here is the test is creating a volume type and then creating a volume with that type.

next it deletes the volume type.

so now, when the volume is deleted and it tries to querie the quota for the volume-type associated with that volume we get an exception because the type no longer exists.

Number of options here:
1. Handle the exception by checking the deleted types when this is encountered
        This will lead to some other issues because of the way the quota resource checks are implemented, and could lead to a bit
         of refactoring in the quota code
2. Don't allow deletion of volume-types that are currently in use
        Rather than delete types that are in use, we error with "can't delete in use resource" or something like that
        We could offer up something like a "disable-type" so that a type that admins don't want used any longer will be disabled but
        still exist until they're no longer in use.

Personally I like option 2, it seems like more intuitive behavior, I'd like to get some input from folks and maybe throw out a proposal shortly to see what others think.