Comment 2 for bug 1305550

There was quite a bit of debate around this, we might want to consider a "list-valid-types" for a volume, otherwise this becomes a bit of a guessing game and we litter the users env with volumes in an "error" state that they can't use.

The other option is a sub-status (last operation status) since there are cases where the volume is "ok" but it couldn't complete an operation.

I'm not crazy about just changing the status to 'error' only because we don't give the end user a method to know what to do here.