Project

General

Profile

Actions
Copy link

Bug #1584

closed

rgw: swift key management is busted

Added by Sage Weil over 12 years ago. Updated over 6 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
-
Target version:
-
% Done:

0%

Source:
Tags:
Backport:
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:
Crash signature (v1):
Crash signature (v2):

Description

from wodrich: "just to make sure, I created a key on matwod-dev2 and it didn't have any anomalies displaying the swift_key, I tried creating another one, but it just overwrote the first (I guess they can only have one swift key at the moment?) and I tried again with --gen-access-key=false and --gen-secret=false, but that didn't stop it from generating them anyway. I have cleaned up the 5 extra keys I made on matwod-dev2, but it seems there's no way to stop radosgw_admin key create from adding an s3 key right now"

- only one key at a time
- secret sometimes mangled?
- --gen-* flags don't seem to work right?
- adds s3 key too?

Actions
Copy link
 #1

Updated by Sage Weil over 12 years ago

  • Target version changed from v0.37 to v0.38
Actions
Copy link
 #2

Updated by Sage Weil over 12 years ago

  • Translation missing: en.field_position set to 922
Actions
Copy link
 #3

Updated by Yehuda Sadeh over 12 years ago

  • Status changed from New to Resolved

We can now hold multiple swift keys, and multiple S3 keys. There's one swift key per subuser, and we can specify key type when creating/removing key. This will generate a random swift key for foo:bar subuser:

radosgw-admin key create --subuser=foo:bar --key-type=swift

key-type defaults to s3 to retain backward compatibility.

Actions
Copy link
 #4

Updated by John Spray over 6 years ago

  • Project changed from Ceph to rgw
  • Category deleted (22)
  • Target version deleted (v0.38)

Bulk reassign of radosgw category to RGW project.

Actions
Copy link

Also available in: Atom PDF