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 2395210

Summary:	[server-access-logging] improve error message when log bucket fails in journal mode
Product:	[Red Hat Storage] Red Hat Ceph Storage	Reporter:	Yuval Lifshitz <ylifshit>
Component:	RGW	Assignee:	Yuval Lifshitz <ylifshit>
Status:	CLOSED ERRATA	QA Contact:	Hemanth Sai <hmaheswa>
Severity:	medium	Docs Contact:	Rivka Pollack <rpollack>
Priority:	unspecified
Version:	8.1	CC:	ceph-eng-bugs, cephqe-warriors, hmaheswa, rpollack, vimishra
Target Milestone:	---
Target Release:	9.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	ceph-20.1.0-18	Doc Type:	Enhancement
Doc Text:	.Clear error propagation for logging failures in journal mode Previously, when logging failed in journal mode, the customer received generic or misleading error messages. For example, a customer performing a regular S3 operation could see a 403 error if permissions were missing on the log bucket, even though permissions were correct on the target bucket. With this enhancement, the system now propagates a clear error message indicating that the failure occurred during logging, not the primary operation. As a result, customers can quickly identify and resolve logging-related issues without confusion.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2026-01-29 06:59:18 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:
Bug Depends On:
Bug Blocks:	2388233

Description Yuval Lifshitz 2025-09-15 13:42:06 UTC

in journal mode, when logging fails, a failure is replied to the client doing the original op.
however, this would be confusing for the client.
e.g. if the log bucket does not have proper logging policy, and the client is doing a PUT opearion on their bucket, we will reply with HTTP 403 to the client.
this is confusing, because the client have PUT permissions to theit bucket, and there is no indication that the permission problem is on the log bucket.

Comment 7 errata-xmlrpc 2026-01-29 06:59:18 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 (Moderate: Red Hat Ceph Storage 9.0 Security 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-2026:1536