| Thread Previous • Date Previous • Date Next • Thread Next |
Public bug reported:
Copying of larger images using copy-image import method fails for AWS S3
store. The reason is while copying the image it uses 'single_part'
upload for uploading large images. On normal image creation process it
does uses 'multi_part' upload and thus works fine.
After further analyzing the code in glance, image size is not passed to
[1] which is required to decide the upload mechanism on S3 side.
[1]
https://github.com/openstack/glance_store/blob/master/glance_store/_drivers/s3.py#L628
Possible solution:
Since we have image size available at the time of copying the image, we
should pass it all the way to s3 driver through onion layer of glance.
** Affects: glance
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Glance.
https://bugs.launchpad.net/bugs/2051914
Title:
Copying existing image to AWS S3 fails for files larger than 5GB
Status in Glance:
New
Bug description:
Copying of larger images using copy-image import method fails for AWS
S3 store. The reason is while copying the image it uses 'single_part'
upload for uploading large images. On normal image creation process it
does uses 'multi_part' upload and thus works fine.
After further analyzing the code in glance, image size is not passed
to [1] which is required to decide the upload mechanism on S3 side.
[1]
https://github.com/openstack/glance_store/blob/master/glance_store/_drivers/s3.py#L628
Possible solution:
Since we have image size available at the time of copying the image,
we should pass it all the way to s3 driver through onion layer of
glance.
To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/2051914/+subscriptions
| Thread Previous • Date Previous • Date Next • Thread Next |
