.Users can now configure the remote S3 service with the right credentials
Previously, while configuring remote cloud S3 object store service to transition objects, access keys starting with digit were incorrectly parsed. Due to this, there were chances for the object transition to fail.
With this fix, the keys are parsed correctly. Users cannot configure the remote S3 service with the right credentials for transition.
Description of problem:
While configuring cloud-tier, if the access key/secret starts with digit, it may get trimmed.
For eg.,
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",
This is due to a bug in JSONParser::parse() which is fixed in the upstream
Tracker: https://tracker.ceph.com/issues/55212
Fix: https://github.com/ceph/ceph/pull/35870
Version-Release number of selected component (if applicable):
How reproducible:
Steps to Reproduce:
1.
2.
3.
Actual results:
Expected results:
Additional info:
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory (Moderate: Red Hat Ceph Storage 6.1 security and bug fix update), and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHSA-2023:3623
Comment 11Red Hat Bugzilla
2023-10-14 04:25:43 UTC
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days
Description of problem: While configuring cloud-tier, if the access key/secret starts with digit, it may get trimmed. For eg., 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", This is due to a bug in JSONParser::parse() which is fixed in the upstream Tracker: https://tracker.ceph.com/issues/55212 Fix: https://github.com/ceph/ceph/pull/35870 Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info: