Hi Gaëtan,
Glance team doesn't recommend to use OSC anymore. I will recommend you to check the same behaviour using python-glanceclient.
Thanks & Best Regards,
Abhishek Kekane
On Sat, Feb 29, 2020 at 3:54 AM Monty Taylor mordred@inaugust.com wrote:
On Feb 28, 2020, at 4:15 PM, gaetan.trellu@incloudus.com wrote:
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.
WOW.
I still don’t know the issue - but my unfounded hunch is that the curl command is likely not doing something it should be. If OSC is producing a file that matches the image details, that seems like the right choice for now.
Seriously fascinating though.
Gaëtan
On 2020-02-28 17:00, Monty Taylor wrote:
On Feb 28, 2020, at 2:29 PM, gaetan.trellu@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-bin...