Comment 1 for bug 1587108

Matthew Booth has also reproduced this issue, and noting his comments from the downstream bug here:

-------------
I just reproduced this in devstack, and this looks like a real bug to me. The issue is the image metadata generated when creating the snapshot.

In my reproducer, I've created a volume from a cirros image with no min_disk. I booted a flavor with a 2G root disk, although obviously that root disk is not created when booting from volume. I then snapshotted the instance. The resulting image metadata in the snapshot contains:

min_disk | 2
min_ram | 0
size | 0

I assume that min_disk here has been copied from the flavor size. This is obviously bogus. I believe that when we create the snapshot metadata we should copy image metadata from the source, and set size to the actual size.

Just to clarify, in the above reproducer I think that the bug has occurred by the time the snapshot is created. That may mean that the bug is in the creation of the snapshot, or it may mean that some metadata copied during that process is already wrong and the bug happened even earlier.

A workaround would be to update the image metadata of the snapshot to set min_disk to 0.
-------------