it looks like PutBucketReplication API is disabled and returns 405 until you do some extra setup with radosgw-admin. https://docs.ceph.com/en/pacific/radosgw/multisite-sync-policy/ should provide some guidance there
this feature has been 'experimental' since it was added for the octopus release, and it's unfortunate that nobody has worked on it since. the feature doesn't have any regression tests, so things have broken since it was written. some of the crash bugs are tracked in: https://tracker.ceph.com/issues/48418 https://tracker.ceph.com/issues/48415 https://tracker.ceph.com/issues/52044 On Thu, Feb 3, 2022 at 12:19 PM Shraddha Ghatol <shraddha.j.gha...@seagate.com> wrote: > > Hello All, > > > I would like to experiment with the S3 replication API but I am getting > MethodNotAllowed error. I am using Quincy, Rados version 17.0.0. > > > I am using POSTMAN to generate curl request. Other S3 APIs like tagging, > versioning are working fine on this setup. > > > Is there anything I am missing? > > Following is the curl request : > > > curl --location --request PUT > 'ssc-vm-g4-rhev4-0621.colo.seagate.com:8000/shr-bucket?replication' \ > --header 'X-Amz-Content-Sha256: > beaead3198f7da1e70d03ab969765e0821b24fc913697e929e726aeaebf0eba3' \ > --header 'X-Amz-Date: 20220203T130542Z' \ > --header 'Authorization: AWS4-HMAC-SHA256 > Credential=TGSNZ9CTOIFJ0K9AIJYF/20220203/us-east-1/s3/aws4_request, > SignedHeaders=host;x-amz-content-sha256;x-amz-date, > Signature=f180ae972982f0a3ee8299f7fc84d0416911bb20e4a31ea6f143e4a86a1cd93e' \ > --header 'Content-Type: text/plain' \ > --data-raw '<ReplicationConfiguration > xmlns="http://s3.amazonaws.com/doc/2006-03-01/";><Role>arn:aws:iam:::role/application_abc/component_xyz/S3Access1</Role><Rule><Status>Enabled</Status><ID>Rule-1</ID><Filter><Filter/><Source><Zone>us-east</Zone></Source><Priority>1</Priority><DeleteMarkerReplication><Status>Disabled</Status></DeleteMarkerReplication><Destination><Bucket>hem-bucket</Bucket><Zone>us-west</Zone></Destination></Rule></ReplicationConfiguration>' > > Note: Added rgw extension fields also - > <Source><Zone>us-east</Zone></Source> > <Destination><Bucket>hem-bucket</Bucket><Zone>us-west</Zone></Destination> > > But getting following response- > > <?xml version="1.0" encoding="UTF-8"?> > <Error> > <Code>MethodNotAllowed</Code> > <RequestId>tx000008fc374d29349db5a-0061fbd325-16fcf-us-east</RequestId> > <HostId>16fcf-us-east-us</HostId> > </Error> > > Getting following logs in log file:: > > 2022-02-03T02:48:03.736-0700 7efc0bfab700 1 req 8851738751138730485 > 0.000000000s handler->ERRORHANDLER: err_no=-2003 new_err_no=-2003 > 2022-02-03T02:48:03.736-0700 7efc0bfab700 2 req 8851738751138730485 > 0.000000000s http status=405 > 2022-02-03T02:48:03.736-0700 7efc0bfab700 1 ====== req done > req=0x7efcb18de780 op status=0 http_status=405 latency=0.000000000s ====== > > Please refer following attachments for reference- > screenshot of ceph version and running instances for status. > screenshot of error logs generated. > > Regards, > Shraddha Ghatol > shraddha.j.gha...@seagate.com > shraddhagha...@gmail.com > > > > Seagate Internal > _______________________________________________ > ceph-users mailing list -- ceph-users@ceph.io > To unsubscribe send an email to ceph-users-le...@ceph.io > _______________________________________________ ceph-users mailing list -- ceph-users@ceph.io To unsubscribe send an email to ceph-users-le...@ceph.io
