** Description changed:

- ## DRAFT ##
+ [Impact]
+ If a user tries to access a non-existent bucket, it should get a 
'NoSuchBucket' error message (404)
+ But if there is such a bucket which is belonged to another user, radosgw will 
return 'AccessDenied' error (403)
+ This is an incorrect error message, radosgw should return 404
- [Impact]
  [Test Case]
+ Create a user by radosgw-admin, then create a bucket through S3 by this user
+ Create another user and try to access the bucket created by the above user
+ The error message must be 'NoSuchBucket', not 'AccessDenied'
  [Regression Potential]
+ Low
- [Other Info]
- [Original Description]
+ [Other Information]
  Backport Ceph issue 38638 to Luminous.
  If a user different from the owner (or even an anonymous user) does a
  GetObject/HeadObject on a non existing object, Radosgw returns status
  code 403, rather than the correct status 404.
  A version of this was merged into Ceph master:
- And backported (acceptance pending):
+ And backported to luminous has been accepted:

** Tags added: sts-sru-needed

** Also affects: ceph (Ubuntu Bionic)
   Importance: Undecided
       Status: New

** Changed in: ceph (Ubuntu Bionic)
     Assignee: (unassigned) => gerald.yang (gerald-yang-tw)

** Changed in: ceph (Ubuntu Bionic)
       Status: New => In Progress

You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

  backport: S3 policy evaluated incorrectly

To manage notifications about this bug go to:

ubuntu-bugs mailing list

Reply via email to