-
Notifications
You must be signed in to change notification settings - Fork 79
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
Healthcheck is not reporting error for buckets with out access #8428
Comments
@anandhu-karattu I didn't add it yet, this is a duplicate of #8240. |
@anandhu-karattu @romayalon When config.NC_DISABLE_ACCESS_CHECK = false, All the buckets that dont have access are getting listed in |
@naveenpaul1 on step 5 of the bug they set back NC_DISABLE_ACCESS_CHECK=false |
@romayalon, I and @anandhu-karattu had a call and we could see access restricted buckets are listed in invalid_buckets when |
@naveenpaul1 I don't know what was mentioned in the meeting, but -
3. Here is a reproduction of Anandhu's bug -
you can see here that the account is on invalid_accounts but the bucket is on valid_buckets.. |
Environment info
Actual behavior
This test includes parameter "NC_DISABLE_ACCESS_CHECK=true"
Expected behavior
Steps to reproduce
set "NC_DISABLE_ACCESS_CHECK=true"
Create an account with proper access to its newbuckets path. (account-3)
Create a new directory with owner as root and mod bits 770
[root@522new-41 ~]# ls -ld /mnt/gpfs0/buck3/
drwxrwx---. 2 root root 4096 Oct 3 11:20 /mnt/gpfs0/buck3/
Create a bucket with account-3. This succeeds as the RW access check is turned off.
Change "NC_DISABLE_ACCESS_CHECK=false"
All other accounts with no access to --newbuckets path are shown as error. However buck3 is not showing any error as part of health check.
More information - Screenshots / Logs / Other output
The text was updated successfully, but these errors were encountered: