Project

General

Profile

Actions
Copy link

Bug #1855

closed

Creation of a subuser that appears to own an s3 key is possible, and removing the subuser with --purge-keys does not appear to remove the s3 key

Added by Matthew Wodrich over 12 years ago. Updated over 11 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
caleb miles
Target version:
Ceph - v0.51
% Done:

70%

Source:
Tags:
Backport:
Regression:
Severity:
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:
Crash signature (v1):
Crash signature (v2):
Actions
Copy link
 #1

Updated by Yehuda Sadeh over 12 years ago

  • Category set to 22
Actions
Copy link
 #2

Updated by Yehuda Sadeh over 11 years ago

  • Assignee set to caleb miles
Actions
Copy link
 #3

Updated by Sage Weil over 11 years ago

  • Project changed from Ceph to rgw
  • Category deleted (22)
Actions
Copy link
 #4

Updated by Yehuda Sadeh over 11 years ago

  • Target version set to Ceph - v0.51
Actions
Copy link
 #5

Updated by caleb miles over 11 years ago

  • Status changed from New to 12

This bug can be reproduced by using the following options

./radosgw-admin -c {'ceph.conf'} --rgw-socket-path=/tmp/rgw.socket -f --log-to-stderr subuser create --uid={'user_id'} 
    --subuser={'subuser_name'} --key-type=s3 --access-key={'some_access_key'} --secret={'some_secret_key'}
Actions
Copy link
 #6

Updated by caleb miles over 11 years ago

  • % Done changed from 0 to 70
Actions
Copy link
 #7

Updated by Yehuda Sadeh over 11 years ago

  • Status changed from 12 to Resolved

Commit 5db3a9e71c6b757660d0702efada40af6be63eb8 pushed. We disallow creating s3 key when subuser is created in order to avoid any confusion. Subusers are swift.

Actions
Copy link

Also available in: Atom PDF