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 2359211

Summary:	Restrict addition of namespaces with RBD images which are already part of other NVMeOF GW groups as namespaces to avoid data corruption
Product:	[Red Hat Storage] Red Hat Ceph Storage	Reporter:	Rahul Lepakshi <rlepaksh>
Component:	NVMeOF	Assignee:	Aviv Caro <acaro>
Status:	CLOSED UPSTREAM	QA Contact:	JAYA PRAKASH P <jprakash>
Severity:	urgent	Docs Contact:	Rivka Pollack <rpollack>
Priority:	unspecified
Version:	7.1	CC:	acaro, aindenba, bdavidov, bkunal, cephqe-warriors, gbregman, jcaratza, jprakash, kjosy, lchernin, linuxkidd, pdhange, rpollack, vumrao
Target Milestone:	---	Keywords:	External
Target Release:	9.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:	.Using the same Ceph Block Device images in multiple NVMe-oF gateway groups no longer results in data corruption and inconsistent behavior Previously, using the same Ceph Block Device (RBD) image in multiple NVMe-oF gateway groups could lead to data corruption and inconsistent behavior because the system allowed duplicate namespace creation across gateway groups. With this fix, the NVMe-oF subsystem now prevents adding an RBD image to a namespace if that image is already associated with another gateway group. Attempts to reuse an image fail with an error message that identifies the conflicting namespace. A `--force` option is available for exceptional cases, but should only be used with caution. As a result, namespace creation no longer succeeds when an RBD image is already in use by another NVMe-oF gateway group, reducing the risk of data corruption.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2026-03-04 09:52:16 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 Rahul Lepakshi 2025-04-12 06:58:08 UTC

Description of problem:
This might be tough to implement as RBD image metadata are part of different omap state files but we need to find a way to restrict creation of namespaces with RBD images which are already part of other GW groups as namespaces, as these volumes can be accessed by multiple clients causing data inconsistency. With huge scale, say 1K to 4K RBD images, it will be difficult for customer to keep track of used/unused images to create namespaces 


Version-Release number of selected component (if applicable):
ceph version 19.1.0-42.el9cp
cp.stg.icr.io/cp/ibm-ceph/nvmeof-rhel9:1.2.17-11


How reproducible: Always


Steps to Reproduce:
1. Deploy 4 nvmeof services with 4 GW groups having 2+ Gateways
2. Configure subsystems and add namespaces with a set of RBD images within a Gateway group
3. On other GW group, configure subsystems and add namespaces with same set of namespaces

Actual results: Same RBD images can be used to create namespaces in different GW groups


Expected results: Namespace addition should never succeed with RBD image already used by namespace in other GW group


Additional info:

Comment 3 Gil Bregman 2025-07-27 09:00:50 UTC

Done in PR #1367

Comment 9 Red Hat Bugzilla 2026-03-04 09:52:16 UTC

This product has been discontinued or is no longer tracked in Red Hat Bugzilla.