You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ozone.apache.org by "Xiaoyu Yao (Jira)" <ji...@apache.org> on 2020/05/13 23:16:00 UTC
[jira] [Resolved] (HDDS-3327) BUCKET_NOT_FOUND occurs when I create
the bucket using the aws s3api
[ https://issues.apache.org/jira/browse/HDDS-3327?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Xiaoyu Yao resolved HDDS-3327.
------------------------------
Fix Version/s: 0.6.0
Resolution: Fixed
Thanks [~micahzhao] for the contribution and all for the reviews. The PR has been merged to master.
> BUCKET_NOT_FOUND occurs when I create the bucket using the aws s3api
> --------------------------------------------------------------------
>
> Key: HDDS-3327
> URL: https://issues.apache.org/jira/browse/HDDS-3327
> Project: Hadoop Distributed Data Store
> Issue Type: Bug
> Components: S3
> Affects Versions: 0.5.0
> Reporter: mingchao zhao
> Assignee: mingchao zhao
> Priority: Major
> Labels: pull-request-available
> Fix For: 0.6.0
>
> Attachments: error.log
>
>
> 1、When the acl is enabled(not enable security), It report an error to execute the following command to create the bucket. This is successful when the acl is not enabled.
> {code:java}
> aws s3api --endpoint-url http://localhost:9878 create-bucket --bucket=bucket1
> {code}
> The error log is in the attachment.
> 2、Besides, acl initialization is still a problem in ozone. Before the old cluster enabled acls, the acl of the old key(created through s3g)will set to the s3g startup user, which should be set to AccesskeyId. Because the AccesskeyId is used as the user name to access these keys when the acl is enabled.
> The reason for the above two problems is the same, I will use a PR to fix it
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: ozone-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: ozone-issues-help@hadoop.apache.org