Project

General

Profile

Actions
Copy link

Bug #43056

closed

pubsub s3 records pushed to an endpoint don't match documentation

Added by Yuval Lifshitz over 4 years ago. Updated about 4 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Yuval Lifshitz
Target version:
-
% Done:

0%

Source:
Development
Tags:
Backport:
nautilus
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
rgw
Pull request ID:
31926
Crash signature (v1):
Crash signature (v2):

Description

docs has: https://docs.ceph.com/docs/master/radosgw/notifications/#events

{"Records":[
  {
    "eventVersion":"2.1" 
    "eventSource":"aws:s3",
    "awsRegion":"",
    "eventTime":"",
    "eventName":"",
    "userIdentity":
  }
]}

while actual events are:
{
  "eventVersion":"2.1",
  "eventSource":"aws:s3",
  "awsRegion":"",
  "eventTime":"2019-11-27T13:48:54.974829Z",
  "eventName":"s3:ObjectCreated:Put",
  "userIdentity":
  ...
}

Related issues 1 (0 open — 1 closed)

Copied to rgw - Backport #43168: nautilus: pubsub s3 records pushed to an endpoint don't match documentationResolvedNathan CutlerActions
Actions
Copy link
 #1

Updated by Yuval Lifshitz over 4 years ago

  • Status changed from New to Fix Under Review
  • Pull request ID set to 31926

note that the correct format was used when events were pulled from Ceph (both for S3-compliant and non-compliant modes), and problem exists when events are pushed to an endpoint (again, in both modes).
In current endpoint implementations the events are not batched, but in the future they may be batched. In such a case the fix has importance beyond compatibility issues, as it would allow multiple events to be batched in one message (similarly to pull mode).

Actions
Copy link
 #2

Updated by Casey Bodley over 4 years ago

  • Status changed from Fix Under Review to Pending Backport
Actions
Copy link
 #3

Updated by Nathan Cutler over 4 years ago

  • Copied to Backport #43168: nautilus: pubsub s3 records pushed to an endpoint don't match documentation added
Actions
Copy link
 #4

Updated by Nathan Cutler about 4 years ago

  • Status changed from Pending Backport to Resolved

While running with --resolve-parent, the script "backport-create-issue" noticed that all backports of this issue are in status "Resolved" or "Rejected".

Actions
Copy link

Also available in: Atom PDF