I don't know that Glance needs to check this. The data at the location is out of Glance's control, so even if glance checked at the time the image was added, the bits at the location could be changed. The immutability guarantee is that once an image goes active, the image's UUID is associated with a particular set of bits that can be confirmed by the checksum. But the prudent image consumer will verify the image bits using the checksum, because they may have become corrupted in transit.
I don't know that Glance needs to check this. The data at the location is out of Glance's control, so even if glance checked at the time the image was added, the bits at the location could be changed. The immutability guarantee is that once an image goes active, the image's UUID is associated with a particular set of bits that can be confirmed by the checksum. But the prudent image consumer will verify the image bits using the checksum, because they may have become corrupted in transit.
Or am I misunderstanding the bug?