Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

This project is now read‑only. Starting Monday, February 2, please use https://ibm-ceph.atlassian.net/ for all bug tracking management.

Bug 1873881

Summary:	When Kafka Cluster is unavailable, Bucket access is not available after setting up Bucket Notification feature.
Product:	[Red Hat Storage] Red Hat Ceph Storage	Reporter:	Avi Mor <avmor>
Component:	RGW	Assignee:	Yuval Lifshitz <ylifshit>
Status:	CLOSED ERRATA	QA Contact:	Madhavi Kasturi <mkasturi>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	4.1	CC:	aavraham, cbodley, ceph-eng-bugs, gsitlani, kbader, maugarci, mbenjamin, mhackett, mkasturi, sweil, tserlin, vereddy, ylifshit
Target Milestone:	---
Target Release:	4.2z1
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:	ceph-14.2.11-130.el8cp, ceph-14.2.11-130.el7cp	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2021-04-28 20:12:31 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Avi Mor 2020-08-30 18:42:09 UTC

Description of problem:

If the Kafka Cluster is unavailable, after setting the Bucket Notification feature, requests get stuck, and requests to write or read requests are not allowed.

Version-Release number of selected component (if applicable):
14.2.8-50.el7cp

How reproducible:

- Create a Kafka cluster. Configure Bucket Notification on the required bucket. Shut down the Kafka cluster, you will be note that the writes/reads to the bucket are get stuck while the Kafka cluster is not available. 

Steps to Reproduce:
1. Create a Kafka cluster
2. Configure Bucket Notification on the required bucket
3. Check that requests get stuck.

Actual results:
Requests are get stuck while the Kafka cluster is not available. 
Expected results:
I would expect that even if the Kafka Cluster is not available, the writing and readings to Bucket will still be available.

Additional info:

Comment 1 Avi Mor 2020-08-30 18:52:05 UTC

Correcting myself, I'm not sure this happens with ״Read״ requests.
But in ״Put״ and ״Delete״, it does create problems.

Thank you,
Avi Mor

Comment 5 Avi Avraham 2020-09-10 14:18:01 UTC

Hi Matt and Yuval

Is it possible to have a fix this issue in the coming release RHCS 4.2 since it a critical for the customer end-users implementations? 
Please let us know if it's a valid request so we will be able to update the customer. 

Thanks 
Avi Avraham 
EMEA storage TAM.

Comment 7 Yuval Lifshitz 2020-09-13 13:04:30 UTC

*** Bug 1859167 has been marked as a duplicate of this bug. ***

Comment 17 Yuval Lifshitz 2021-02-19 13:46:44 UTC

was the topic created with "persistent" flag?

by default the topics are non-persistent (=synchronous), which means that the requests will time out.
when topics are created with "persistent" flags, the requests will be continue until as long as there is space in the notification queue, and then fail immediately with "server busy" response.

Comment 23 errata-xmlrpc 2021-04-28 20:12:31 UTC

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 (Important: 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-2021:1452