Closed anandhu-karattu closed 11 months ago
If I create account with "--uid 0 --gid 0", mb command works fine.
@anandhu-karattu duplicate issue, please close it https://github.com/noobaa/noobaa-core/issues/7633
Marking this ticket as closed (duplicate)
Environment info
Actual behavior
AWS mb command is failing with access denied error. From the noobaa.log it is evident that the create config file for bucket is failing with permission issue (see below for more details). However node command is working with out any issue.
Expected behavior
AWS mb command should create the config files as well as bucket directory successfully.
Steps to reproduce
[root@an2node-x-worker1 certificates]# /usr/local/noobaa-core/bin/node /usr/local/noobaa-core/src/cmd/manage_nsfs account add --name an-test1 --email an-test1@gmail.com --new_buckets_path /mnt/fs1/s3-user234 --uid 234 --gid 234 --access_key a-antest1 --secret_key s-antest1
Create alias for that account
[root@an2node-x-worker1 certificates]# alias aws-antest1="AWS_ACCESS_KEY_ID=a-antest1 AWS_SECRET_ACCESS_KEY=s-antest1 aws --endpoint https://localhost:6443 --no-verify-ssl s3"
Now create a bucket using aws mb command --> FAILING
From the noobaa.log. check for time stamp 2023-12-13T03:08:09.562411-08:00
Possible root cause is due to uid and gid I specified during account creation. That uid does not have access to create config file /gpfs/fs-ces-shared/ces/s3-config/buckets/newbucket-anandhu.json
More information - Screenshots / Logs / Other output