Comment 5 for bug 1457517

I looked at the patch, it seems like it still compares the size of the image that volume was created from with the flavor root disk size. I can understand why this check is needed for the min_ram / flavor memory, but why is it needed for the disk?

I'm afraid of situation where user creates a large snapshot, creates a volume from it, and then is unable to boot it from a flavor that has small memory / disk parameters.