-
Notifications
You must be signed in to change notification settings - Fork 80
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
NC | NSFS | Versioning | Delete of partial directory of nested key results in AccessDeniedError
#8454
Comments
AccessDeniedError
AccessDeniedError
@romayalon same behaiour is tested in version enabled bucket and its working with out creating any issue
cc : @shirady |
@romayalon both noobaa and aws behaving similer, When I try to get object using dir path such as (a/b/c or a/b/c/) its returning Local noobaa behavior
AWS Behavior
|
@naveenpaul1 On NooBaa you tested it on the branch that contains your fix #8480 ? |
yes @romayalon , I did the test with my changes in branch |
Environment info
Actual behavior
AccessDenied
and in FS layer it isError: Operation not permitted, code: 'EPERM'
Expected behavior
Steps to reproduce
sudo node src/cmd/manage_nsfs account add --name <account-name> --new_buckets_path /tmp/nsfs_root1 --access_key <access-key> --secret_key <secret-key> --uid <uid> --gid <gid>
Note: before creating the account need to give permission to the
new_buckets_path
:chmod 777 /tmp/nsfs_root1
,chmod 777 /tmp/nsfs_root2
.sudo node src/cmd/nsfs --debug 5
Notes:
config.NSFS_CHECK_BUCKET_BOUNDARIES = false; //SDSD
because I’m using the/tmp/
and not/private/tmp/
.alias nc-user-1-s3=‘AWS_ACCESS_KEY_ID=<access-key> AWS_SECRET_ACCESS_KEY=<secret-key> aws --no-verify-ssl --endpoint-url https://localhost:6443’
.nc-user-1-s3 s3 ls; echo $?
nc-user-1-s3 s3 mb s3://bucket-v
(bucket-v
is the bucket name in this example)nc-user-1-s3 s3api put-bucket-versioning --bucket bucket-v --versioning-configuration Status=Enabled
nc-user-1-s3 s3api put-object --bucket bucket-v --key /a/b/c/lala.txt
nc-user-1-s3 s3api delete-object --bucket bucket-v --key /a/b/c
Note: deleting the directory creates the delete marker as expected (
nc-user-1-s3 s3api delete-object --bucket bucket-v --key /a/b/c/
).More information - Screenshots / Logs / Other output
Might be that this issue is with the same root cause of the issue - #8320
The text was updated successfully, but these errors were encountered: