Comment 5 for bug 1533536

In v1, if the image's checksum is not equal to the checksum which users provide, the image will be killed.

But in v2. we create an image with two steps: create a queued image, then upload the data.

At client view, when use
  $ glance image-create --checksum 123abc --file /tmp/myimage
the image should be killed to keep the same with v1.

But if a user take two steps to do image-create. Maybe there is a problems:
image-upload should support checksum input. if the checksum is a wrong one. should the image be killed? At least IMO, the queued image should not be deleted. If so, it will be different from v1.

Maybe we should be cautious to introduce checksum into v2.