Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
This project is now read‑only. Starting Monday, February 2, please use https://ibm-ceph.atlassian.net/ for all bug tracking management.

Bug 2402662

Summary: [IBM_Support][CLOUDTIER] Transitioning ceph data to Amazon S3 is failing
Product: [Red Hat Storage] Red Hat Ceph Storage Reporter: Velumurugan R <ver>
Component: RGWAssignee: Soumya Koduri <skoduri>
Status: CLOSED ERRATA QA Contact: Vidushi Mishra <vimishra>
Severity: medium Docs Contact: Rivka Pollack <rpollack>
Priority: unspecified    
Version: 8.1CC: assingh, bkunal, ceph-eng-bugs, cephqe-warriors, ckulal, jcaratza, josgutie, kjosy, rpollack, skoduri, vimishra
Target Milestone: ---   
Target Release: 9.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: ceph-20.1.0-81 Doc Type: Bug Fix
Doc Text:
.Data transition to AWS non-default regions is now supported Previously, the cloud tier module did not handle the location_constraint parameter required by AWS when creating a bucket in a non-default region. As a result, data transition to an AWS cloud endpoint failed if the target bucket was in a non-default region. With this fix, a new parameter, `location_constraint`, has been added to the `tier_config` configuration. This parameter must be set or updated along with region when using AWS non-default regions. Data can now be transitioned to AWS non-default regions successfully.
Story Points: ---
Clone Of:
: 2412416 (view as bug list) Environment:
Last Closed: 2026-01-29 07:01:34 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 2388233, 2412416    

Comment 17 Velumurugan R 2025-10-23 09:38:49 UTC
Hi Team,


 The Customer finally realises that transition was blocked by firewall and the transition is successful, but it creates the aws object key with aws_bucketname/rgw_bucketname/object_name under the aws bucket. it is expected to have rgw_bucketname/object_name under aws bucket name. 

The actual object key under the aws bucket --> s3://velulctest/velulctest/iniy/1mbfile 
The expected object ket key under the aws bucket --> s3://velulctest/iniy/1mbfile 


As soumya kodhuri suggested, we tried the transition without the target path, transition added a new name inbetween. 

s3://velulctest/rgwx-default-cloudtier-cloud-bucket/alu/1mbfile. 

"s3": {
                            "endpoint": "http://velulctest.s3-eu-west-1.amazonaws.com",
                            "access_key": "AKIATZZEJESLTHJBRU2N",
                            "secret": "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",
                            "region": "eu-west-1",
                            "host_style": "path",
                            "target_storage_class": "",
                            "target_path": "",
                            "acl_mappings": [],
                            "multipart_sync_threshold": 44432,
                            "multipart_min_part_size": 44432
                        },


Could you please help us to store the aws object key with s3://awsbucketname/rgwbucketname/objectname ?


Regards
Velmurugan

Comment 30 errata-xmlrpc 2026-01-29 07:01:34 UTC
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 9.0 Security and Enhancement 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-2026:1536