Actions
Bug #51293
closednotifications: notifications stop working after bucket reshard
% Done:
100%
Source:
Q/A
Tags:
notifications backport_processed
Backport:
octopus pacific
Regression:
No
Severity:
3 - minor
Reviewed:
Description
any new notifications which is created after the reshard, will work
Updated by Yuval Lifshitz almost 3 years ago
- Status changed from In Progress to Fix Under Review
- Pull request ID set to 41956
Updated by Yuval Lifshitz almost 3 years ago
steps to verify:
- run HTTP endpoint on port 10900
- start cluster
- create topic, notifications and make sure that the notification is sent top the HTTP endpoint
aws --endpoint-url http://localhost:8000 sns create-topic --name=fishtopic --attributes='{"push-endpoint": "http://localhost:10900"}' aws --endpoint-url http://localhost:8000 s3 mb s3://fish aws --region=default --endpoint-url http://localhost:8000 s3api put-bucket-notification-configuration --bucket fish --notification-configuration='{"TopicConfigurations": [{"Id": "notif1", "TopicArn": "arn:aws:sns:default::fishtopic", "Events": []}]}' aws --endpoint-url http://localhost:8000 s3 cp hello.txt s3://fish - do a reshard:
bin/radosgw-admin bucket reshard --num-shards 17 --bucket fish
- make sure notification is still sent:
aws --endpoint-url http://localhost:8000 s3 cp hello.txt s3://fish
Updated by Casey Bodley almost 3 years ago
- Status changed from Fix Under Review to Pending Backport
- Backport set to octopus pacific
Updated by Backport Bot almost 3 years ago
- Copied to Backport #51349: octopus: notifications: notifications stop working after bucket reshard added
Updated by Backport Bot almost 3 years ago
- Copied to Backport #51350: pacific: notifications: notifications stop working after bucket reshard added
Updated by Backport Bot over 1 year ago
- Tags changed from notifications to notifications backport_processed
Updated by Konstantin Shalygin about 1 year ago
- Status changed from Pending Backport to Resolved
- % Done changed from 0 to 100
Actions