Hi Thilo, The issue was indeed fixed (both with regard to filtering and sending the metadata) in the tracker that you mentioned but was broken by another fix ( https://github.com/ceph/ceph/pull/39192) :-( I will re-apply the fix (and make sure we regression tests, so it does not break again). Yuval On Sat, Nov 12, 2022 at 1:30 PM Thilo-Alexander Ginkel <thilo@xxxxxxxxxx> wrote: > Hi there, > > we are using a Ceph Quincy installation with configured S3 bucket > notifications (without any filters) on the rgw where we are seeing the > phenomenon that the bucket notification JSON is lacking the metadata > attached to the object for the following notification events: > > * ObjectCreated:Copy > * ObjectCreated:CompleteMultipartUpload > > Instead we are only seeing headers of the request that triggered the > notification like: x-amz-content-sha256, x-amz-copy-source and x-amz-date > > The target object contains the correct metadata when checking afterwards > (using HeadObject). > > Have we hit a bug or are missing something obvious? > > A similar issue seems to have been fixed in the past (but had a focus on > filtering) and is documented in https://tracker.ceph.com/issues/51261. > > Thanks & kind regards, > Thilo > _______________________________________________ > ceph-users mailing list -- ceph-users@xxxxxxx > To unsubscribe send an email to ceph-users-leave@xxxxxxx > > _______________________________________________ ceph-users mailing list -- ceph-users@xxxxxxx To unsubscribe send an email to ceph-users-leave@xxxxxxx
 |