Project

General

Profile

Actions
Copy link

Bug #58930

closed

Bug in parsing access_key for cloud tier/cloud transition?

Added by Ulrich Klein about 1 year ago. Updated about 1 year ago.

Status:
Won't Fix
Priority:
Normal
Assignee:
-
Target version:
-
% Done:

0%

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

Description

I'm experimenting with "CLOUD TRANSITION" as per https://docs.ceph.com/en/latest/radosgw/cloud-transition/

After a while I got it to work. It took a while because when I enter:

radosgw-admin zonegroup placement modify --rgw-zonegroup=maxzg --placement-id=ec22 --storage-class=CLOUDY --tier-type=cloud-s3 --tier-config=access_key=1MNLI1JA9QM1X7XMGS5R
it outputs:

.....
"s3": {
"endpoint": ...
"access_key": "1",

which obviously won't work

If I do:
radosgw-admin zonegroup placement modify --rgw-zonegroup=maxzg --placement-id=ec22 --storage-class=CLOUDY --tier-type=cloud-s3 --tier-config=access_key=MNLI1JA9QM1X7XMGS5R1
it correctly shows:
"s3": {
"endpoint": ...
"access_key": "MNLI1JA9QM1X7XMGS5R1",

I had to change the access key for the transition so it does not start with a number, as the same happens with all keys that start with a number.

This is with Ceph Quincy 17.2.5

Actions
Copy link

Also available in: Atom PDF