[glance] Different checksum between CLI and curl

gaetan.trellu at incloudus.com gaetan.trellu at incloudus.com
Fri Feb 28 22:15:51 UTC 2020

Hey Monty,

If I download the image via the CLI, the checksum of the file matches 
the checksum from the image details.
If I download the image via "curl", the "Content-Md5" header matches the 
image details but the file checksum doesn't.

The files have the same size, this is really weird.


On 2020-02-28 17:00, Monty Taylor wrote:
>> On Feb 28, 2020, at 2:29 PM, gaetan.trellu at incloudus.com wrote:
>> Hi guys,
>> Does anyone know why the md5 checksum is different between the 
>> "openstack image save" CLI and "curl" commands?
>> During the image creation a checksum is computed to check the image 
>> integrity, using the "openstack" CLI match the checksum generated but 
>> when "curl" is used by following the API documentation[1] the checksum 
>> change at every "download".
>> Any idea?
> That seems strange. I don’t know off the top of my head. I do know
> Artem has patches up to switch OSC to using SDK for image operations.
> https://review.opendev.org/#/c/699416/
> That said, I’d still expect current OSC checksums to be solid. Perhaps
> there is some filtering/processing being done cloud-side in your
> glance? If you download the image to a file and run a checksum on it -
> does it match the checksum given by OSC on upload? Or the checksum
> given by glance API on download?
>> Thanks,
>> Gaëtan
>> [1] 
>> https://docs.openstack.org/api-ref/image/v2/index.html?expanded=download-binary-image-data-detail#download-binary-image-data

More information about the openstack-discuss mailing list