-
Notifications
You must be signed in to change notification settings - Fork 587
HDDS-3765. Fluentd writing to secure Ozone S3 API fails with 500 Error. #1179
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can we add some aws s3 ls and recursive on the same volume/bucket to see how the output will be shown, when files are created with "//" in the smoke test?
|
Working with @bharatviswa504 to hash out details in another related JIRA (HDDS-3955). Based on what is decided, this PR may have some changes. Hoping to get this to a resolution in the next few days. |
|
In HDDS-3955 we are adding new logic that "normalizes" the key when intermediate directories need to be created on createKey API. This fix is good to go now. |
bharatviswa504
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
+1
|
Thanks for the review @bharatviswa504. |
What changes were proposed in this pull request?
While writing to secure Ozone s3 gateway, fluentd fails with 500 Error. This happens when there are extra slashes in the requested object path. (More details are in the JIRA)
What is the link to the Apache JIRA
https://issues.apache.org/jira/browse/HDDS-3765
How was this patch tested?
Manually tested with fluentd s3 plugin.
Added acceptance tests.