Description of problem: Removing bucket notification by sending an empty "NotificationConfiguration" request returns an error. Version-Release number of selected component (if applicable): RHCS 4.2 How reproducible: Steps to Reproduce: 1. Create a bucket 2. configure a bucket notification 3. remove the configuration you just created by sending a request. <NotificationConfiguration> </NotificationConfiguration> Actual results: activity failing with the following error in the RGW log s3:pubsub_notification_create_s3 completing s3:pubsub_notification_create_s3 op status=-2029 s3:pubsub_notification_create_s3 http status=400 req done req=0x7fb402120660 op status=-2029 http_status=400 latency=0.011s ====== beast: 0x7fb402120660: 192.168.42.1 - sds [21/Oct/2021:21:54:06.101 +0000] "PUT /rabbitmq-notifications-sds?notification HTTP/1.1" 400 253 - "Boto3/1.15.15 Python/3.6.8 Linux/4.18.0-305.19.1.el8_4.x86_64 Botocore/1.18.15" - latency=0.011s failed to read header: end of stream Expected results: RGW successfully delete the notification to the relevant bucket Additional info: A reference to the relevant API request in AWS documentation https://docs.aws.amazon.com/AmazonS3/latest/API/API_PutBucketNotificationConfiguration.html
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 Security, Bug Fix, 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-2022:5997