Actions
Bug #22714
openExisting AccessKeys with leading underscore broke in upgrade
% Done:
0%
Source:
Tags:
Backport:
luminous
Regression:
Yes
Severity:
2 - major
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:
Crash signature (v1):
Crash signature (v2):
Description
Pre-existing AccessKeys that start with an underscore broke after the upgrade to Luminous. Newly created keys even identical name are fine.
Workaround:¶
radosgw-admin key rm --uid=$U --access-key=$AK --secret-key=$SK && \ radosgw-admin key create --uid=$U --access-key=$AK --secret-key=$SK
Notes:¶
- New access keys with a leading underscore created in Luminous work fine.
- Recreating the key fixes it.
- Problem might exist in librados layer.
# Broken key, not fixed yet: $ rados -p .users ls |grep _FtBhGSAZABCDEF01234 __FtBhGSAZABCDEF01234 _FtBhGSAZABCDEF01234 # Broken key, after rm & ecreate $ rados -p .users ls |grep _yWcZHmCjgABCDEF01234 __yWcZHmCjgABCDEF01234 _yWcZHmCjgABCDEF01234 _yWcZHmCjgABCDEF01234 # Newly created key with leading underscore: $ rados -p .users ls |grep _LyfrysABCDEF01234 _LyfrysABCDEF01234
Actions