Bug 2069131

Summary: [GSS] Access Denied while listing the bucket using bucket with user user-preferences@bucket.s3
Product: [Red Hat Storage] Red Hat OpenShift Data Foundation Reporter: Priya Pandey <prpandey>
Component: Multi-Cloud Object GatewayAssignee: Nimrod Becker <nbecker>
Status: CLOSED NOTABUG QA Contact: Ben Eli <belimele>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 4.8CC: etamir, hnallurv, ocs-bugs, odf-bz-bot, pibanezr, rcyriac
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-04-08 06:02:56 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
access_denied none

Description Priya Pandey 2022-03-28 10:53:04 UTC 
Created attachment 1868685 [details]
access_denied

Created attachment 1868685 [details]
access_denied

Description of problem (please be detailed as possible and provide log
snippets):


- Cu has created a user named  "user-preferences".

- After that, they've created a bucket named as "user-preferences" bucket

- The user "user-preferences" was given permission to the "user-preferences" bucket that gives access denied.

(Attached screenshot [access_denied] )

- Cu has removed the permission from the user and added it back it worked fine.


- Cu wants to understand the RCA for the issue.


Version of all relevant components (if applicable):

v4.8


Does this issue impact your ability to continue to work with the product
(please explain in detail what is the user impact)?

- Cu has applied the workaround and it's working fine but we want to understand the RCA for this issue.



Is there any workaround available to the best of your knowledge?


- Remove and add the bucket permission to the user.


Rate from 1 - 5 the complexity of the scenario you performed that caused this
bug (1 - very simple, 5 - very complex)?

3

Can this issue reproducible?

In cu environment

Can this issue reproduce from the UI?

N/A

If this is a regression, please provide more details to justify this:

N/A

Steps to Reproduce:
1. Create a user "user-preferences"
2. Create a bucket "user-preferences".
3. Add the bucket permission to this user.


Actual results:

The bucket can't be accessed with the created user.

Expected results:

The bucket should be accessible to the user that holds the permission.

Additional info:

In the next comments