Back to bug 2168540

Who When What Removed Added
Red Hat One Jira (issues.redhat.com) 2023-02-09 11:05:48 UTC Link ID Red Hat Issue Tracker RHCEPH-6118
Milind Changire 2023-02-09 11:07:26 UTC Target Release 6.1z1 5.3z2
Venky Shankar 2023-03-29 11:21:38 UTC Assignee vshankar mchangir
Status NEW ASSIGNED
Greg Farnum 2023-03-29 15:30:03 UTC CC gfarnum
Venky Shankar 2023-03-30 13:52:04 UTC CC vshankar
Target Release 5.3z2 5.3z3
Venky Shankar 2023-04-27 05:47:08 UTC Status ASSIGNED POST
Hemanth Kumar 2023-04-29 10:08:47 UTC Status POST MODIFIED
Flags needinfo?(hyelloji)
Flags needinfo?(vereddy)
CC hyelloji, tserlin, vereddy
Fixed In Version ceph-16.2.10-165.el8cp
Flags needinfo?(hyelloji) needinfo?(vereddy) needinfo+
Hemanth Kumar 2023-05-02 11:12:15 UTC Flags needinfo?(hyelloji)
Flags needinfo?(hyelloji) needinfo-
errata-xmlrpc 2023-05-02 15:04:46 UTC Status MODIFIED ON_QA
Hemanth Kumar 2023-05-08 11:02:34 UTC Status ON_QA VERIFIED
Ranjini M N 2023-05-19 07:16:31 UTC Flags needinfo?(mchangir)
CC rmandyam
Milind Changire 2023-05-19 07:29:51 UTC Flags needinfo?(mchangir)
Doc Type If docs needed, set a value Bug Fix
Doc Text Cause: Pool-level snaps and fs-level snaps have their independent namespaces but both are managed by the mon.

Consequence: Due to namespace collision, this causes a conflict in identifying the namespace to which a snap-id is associated with when a snap-id is passed to the mon during snap deletion.

Fix: The fix is to disable pool-level snap creation for a pool attached to a cephfs instance or disallow attaching of a pool to a cephfs instance when the pool already has pool-level snaps created.

Result: The fix prevents unintentional data loss when snaps are deleted from one namespace when the other namespace was being implied by the user.
Ranjini M N 2023-05-19 12:03:26 UTC Blocks 2203283
Doc Text Cause: Pool-level snaps and fs-level snaps have their independent namespaces but both are managed by the mon.

Consequence: Due to namespace collision, this causes a conflict in identifying the namespace to which a snap-id is associated with when a snap-id is passed to the mon during snap deletion.

Fix: The fix is to disable pool-level snap creation for a pool attached to a cephfs instance or disallow attaching of a pool to a cephfs instance when the pool already has pool-level snaps created.

Result: The fix prevents unintentional data loss when snaps are deleted from one namespace when the other namespace was being implied by the user.
.Prevent unintentional data loss during snap deletion

Previously, due to a namespace collision between pool-level snaps and fs-level snaps, there would be a conflict in identifying the namespace to which a snap-ID was associated when snap-ID was passed to the monitor during snap deletion. This was because the snaps, although had independent namespaces, were managed by the Ceph Monitor.

With this fix, the pool-level snap creation for a pool attached to a Ceph File System (CephFS) is disabled or attaching a pool to a CephFS is disallowed when the pool already has pool-level snaps created. This prevents unintentional loss of data when snaps are deleted from one namespace when the other namespace was implied by the user.
errata-xmlrpc 2023-05-23 00:01:39 UTC Status VERIFIED RELEASE_PENDING
errata-xmlrpc 2023-05-23 00:19:10 UTC Status RELEASE_PENDING CLOSED
Resolution --- ERRATA
Last Closed 2023-05-23 00:19:10 UTC
errata-xmlrpc 2023-05-23 00:19:46 UTC Link ID Red Hat Product Errata RHBA-2023:3259

Back to bug 2168540