minio-multipart-upload #451

New issue

Closed

opened 2024-08-02 09:00:19 +00:00 by alexvanin · 3 comments

alexvanin commented

2024-08-02 09:00:19 +00:00

Owner

frostfs-aio v1.5.0 (frostfs-s3-gw v0.29.0)

minio-multipart-upload mechanism described in https://github.com/tuine/minio-multipart-upload seems broken for s3 gateway. Command below fails with access to object operation denied. as far as I know (didn't test locally).

Please check it on v0.29.0 and v0.30.1 (nightly-v1.6 branch of aio).

curl --location --request PUT 'presigned URL' \
--header 'Content-Type: application/pdf' \
--data 'pathtofile'

frostfs-aio v1.5.0 (frostfs-s3-gw v0.29.0) minio-multipart-upload mechanism described in https://github.com/tuine/minio-multipart-upload seems broken for s3 gateway. Command below fails with `access to object operation denied.` as far as I know (didn't test locally). Please check it on v0.29.0 and v0.30.1 (nightly-v1.6 branch of aio). ``` curl --location --request PUT 'presigned URL' \ --header 'Content-Type: application/pdf' \ --data 'pathtofile' ```

dkirillov was assigned by alexvanin

2024-08-02 09:00:54 +00:00

alexvanin commented

2024-08-02 10:02:04 +00:00

Author

Owner

Maybe some kludge setting should solve it, need to investigate.

Maybe some `kludge` setting should solve it, need to investigate.

dkirillov commented

2024-08-06 08:55:49 +00:00

Member

Couldn't reproduce this error neither on v0.29.x or v0.30.x. But got some other error:

org.simpleframework.xml.core.ValueRequiredException: Unable to satisfy @org.simpleframework.xml.Element(name="PartNumberMarker", type=void.class, data=false, required=true) on field 'partNumberMarker' private int io.minio.messages.ListPartsResult.partNumberMarker for class io.minio.messages.ListPartsResult at line 2

org.simpleframework.xml.core.ValueRequiredException: Unable to satisfy @org.simpleframework.xml.Element(name="NextPartNumberMarker", type=void.class, data=false, required=true) on field 'nextPartNumberMarker' private int io.minio.messages.ListPartsResult.nextPartNumberMarker for class io.minio.messages.ListPartsResult at line 2

and

2024-08-06 11:45:04.009  WARN 598097 --- [nio-8006-exec-1] io.minio.MinioClient                     : S3 service returned unknown XML for CompleteMultipartUpload REST API. <?xml version="1.0" encoding="UTF-8"?>
<CompleteMultipartUploadResult xmlns="http://s3.amazonaws.com/doc/2006-03-01/"><Bucket>test2</Bucket><Key>test/tmp2.txt</Key><ETag>&#34;24c119568a1f9c2d6f2b0fa29a90943a-1&#34;</ETag></CompleteMultipartUploadResult>

Couldn't reproduce this error neither on v0.29.x or v0.30.x. But got some other error: ``` org.simpleframework.xml.core.ValueRequiredException: Unable to satisfy @org.simpleframework.xml.Element(name="PartNumberMarker", type=void.class, data=false, required=true) on field 'partNumberMarker' private int io.minio.messages.ListPartsResult.partNumberMarker for class io.minio.messages.ListPartsResult at line 2 org.simpleframework.xml.core.ValueRequiredException: Unable to satisfy @org.simpleframework.xml.Element(name="NextPartNumberMarker", type=void.class, data=false, required=true) on field 'nextPartNumberMarker' private int io.minio.messages.ListPartsResult.nextPartNumberMarker for class io.minio.messages.ListPartsResult at line 2 ``` and ``` 2024-08-06 11:45:04.009 WARN 598097 --- [nio-8006-exec-1] io.minio.MinioClient : S3 service returned unknown XML for CompleteMultipartUpload REST API. <?xml version="1.0" encoding="UTF-8"?> <CompleteMultipartUploadResult xmlns="http://s3.amazonaws.com/doc/2006-03-01/"><Bucket>test2</Bucket><Key>test/tmp2.txt</Key><ETag>"24c119568a1f9c2d6f2b0fa29a90943a-1"</ETag></CompleteMultipartUploadResult> ```

~~dkirillov referenced this issue 2024-08-06 12:46:52 +00:00~~

feature/451-minio-multiparts-fixes #454

dkirillov referenced this issue

2024-08-08 06:33:51 +00:00

feature/451-minio-multiparts-fixes #454

dkirillov referenced this issue from a commit

2024-08-08 07:55:18 +00:00

Update s3-gw

dkirillov referenced this issue from a commit

2024-08-08 14:26:47 +00:00

[#451] Don't skip [Next]PartNumberMarker in response

dkirillov referenced this issue from a commit