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 2308348

Summary: Add a Prometheus alert for detecting when the same RBD image is used in two or more namespaces within or across GW groups
Product: [Red Hat Storage] Red Hat Ceph Storage Reporter: Rahul Lepakshi <rlepaksh>
Component: NVMeOFAssignee: Vallari <vaagrawa>
Status: CLOSED UPSTREAM QA Contact: Sunil Kumar Nagaraju <sunnagar>
Severity: urgent Docs Contact: ceph-doc-bot <ceph-doc-bugzilla>
Priority: unspecified    
Version: 8.0CC: acaro, aindenba, aviv.caro, bdavidov, bhkaur, bkunal, c7r8j61p, cephqe-warriors, gbregman, kjosy, lchernin, linuxkidd, pdhange, rpollack, vaagrawa, vumrao
Target Milestone: ---Keywords: External
Target Release: 8.1   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Known Issue
Doc Text:
.Restrict adding namespaces with RBD images already assigned to other NVMe-oF gateway groups to avoid data corruption Currently, using the same Ceph Block Device (`rbd`) images in different NVMe-oF gateway groups may lead to unexpected results. As a workaround, avoid using the same Ceph Block Device images in multiple NVMe-oF gateway groups.
 Story Points: ---
Clone Of: Environment:
Last Closed: 2026-03-04 08:54:19 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: 2317218    

Description Rahul Lepakshi 2024-08-28 15:28:01 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 
For now, it is decided to add an alert at 8.1. I raised https://bugzilla.redhat.com/show_bug.cgi?id=2359211 to implement actual resolution 

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 Anon 2024-09-02 03:43:43 UTC 
Can someone please help me with this then. Because I have more docs in my phone.
Comment 7 Vallari 2024-11-20 11:07:59 UTC 
PR opened upstream to add a Prometheus alert for detecting when the same RBD image is used in two or more namespaces: https://github.com/ceph/ceph/pull/60777
Comment 8 Vallari 2025-01-16 11:13:20 UTC 
Merged PR upstream: https://github.com/ceph/ceph/pull/60777 too add prometheus alert NVMeoFMultipleNamespacesOfRBDImage
Comment 9 Vallari 2025-03-18 04:43:45 UTC 
Fixed by https://gitlab.cee.redhat.com/ceph/ceph/-/commit/34c12005834b826c58f8be52ba60ce7549cc0727
Comment 14 Red Hat Bugzilla 2026-03-04 08:54:19 UTC 
This product has been discontinued or is no longer tracked in Red Hat Bugzilla.
Comment 15 Red Hat Bugzilla 2026-03-05 04:27:36 UTC 
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days or the product is inactive and locked