HI Shrishail,

By design copy-image import workflow uses a common uploading mechanism for all stores, so yes it is a known limitation if it is not using multipart upload for s3 backend.

Feel free to propose enhancement for the same or participate in the upcoming PTG 'April 8-12, 2024' to discuss the improvements for this behavior.

Thanks & Best Regards,

Abhishek Kekane

On Wed, Jan 31, 2024 at 3:55 AM Shrishail K <nkshrishail@gmail.com> wrote:

Hi Team,

I have a use case where I need to replicate images from file store to S3 store.

While image creation directly on S3 works fine with large files over 5G.

The same fails when attempted via image-import with copy-image method.

The failure is due to AWS rejecting a single object upload operation where the object size is over 5GB.

What I see from logs is that direct image creation on S3 uses multipart upload when images are large. However, I fail to see the same happening when image import was used to copy an image from file to s3.

Is this a known issue? Or Am I missing some configs related to image-import?

Openstack version: Antelope
Client version: 6.4.0

Thanks,

Shrishail