You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ozone.apache.org by "Janus Chow (Jira)" <ji...@apache.org> on 2023/12/16 23:44:07 UTC

[jira] [Updated] (HDDS-7811) S3 gateway returns 500 instead of NoSuchUpload for FSO bucket

     [ https://issues.apache.org/jira/browse/HDDS-7811?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Janus Chow updated HDDS-7811:
-----------------------------
       Fix Version/s:     (was: 1.4.0)
    Target Version/s: 1.5.0

I am managing the 1.4.0 release and we currently have more than 500 issues targeted for 1.4.0. I am moving the target field to 1.5.0.
       
If you are actively working on this jira and believe this should be targeted for the 1.4.0 release, Please reach out to me via Apache email or Slack.

> S3 gateway returns 500 instead of NoSuchUpload for FSO bucket 
> --------------------------------------------------------------
>
>                 Key: HDDS-7811
>                 URL: https://issues.apache.org/jira/browse/HDDS-7811
>             Project: Apache Ozone
>          Issue Type: Bug
>          Components: OM, S3
>    Affects Versions: 1.3.0
>            Reporter: Ethan Rose
>            Assignee: Ashish Kumar
>            Priority: Major
>              Labels: pull-request-available
>
> When setting the default bucket layout to FSO, the {{Upload part with Incorrect uploadID}} in {{s3/MultipartUpload.robot}} acceptance test fails. This is caused by a {{DIRECTORY_NOT_FOUND OMException}} that is thrown in {{OMKeyCreateRequest#preExecute}} and forwarded to s3 gateway instead of the expected error. The stack trace of the exception is not captured by the current code, but adding OM logging shows:
> {code:java}
> ozonesecure-ha-om1-1  | DIRECTORY_NOT_FOUND org.apache.hadoop.ozone.om.exceptions.OMException: Failed to find parent directory of ozone-test-6048979897/multipartKey
> ozonesecure-ha-om1-1  |         at org.apache.hadoop.ozone.om.request.file.OMFileRequest.getParentID(OMFileRequest.java:1023)
> ozonesecure-ha-om1-1  |         at org.apache.hadoop.ozone.om.request.file.OMFileRequest.getParentID(OMFileRequest.java:973)
> ozonesecure-ha-om1-1  |         at org.apache.hadoop.ozone.om.request.file.OMFileRequest.getParentId(OMFileRequest.java:1055)
> ozonesecure-ha-om1-1  |         at org.apache.hadoop.ozone.om.request.key.OMKeyCreateRequestWithFSO.getDBMultipartOpenKey(OMKeyCreateRequestWithFSO.java:268)
> ozonesecure-ha-om1-1  |         at org.apache.hadoop.ozone.om.request.key.OMyRequest.getFileEncryptionInfoForMpuKey(OMKeyRequest.java:487)
> ozonesecure-ha-om1-1  |         at org.apache.hadoop.ozone.om.request.key.OMKeyCreateRequest.preExecute(OMKeyCreateRequest.java:171)
> {code}
> I was unable to reproduce the exception with modifications to the {{TestOzoneAtRestEncryption}} integration tests.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@ozone.apache.org
For additional commands, e-mail: issues-help@ozone.apache.org