Back to bug 2168541
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| Red Hat One Jira (issues.redhat.com) | 2023-02-09 11:09:26 UTC | Link ID | Red Hat Issue Tracker RHCEPH-6119 | |
| Milind Changire | 2023-02-09 11:10:39 UTC | Target Release | 6.1z1 | 6.1 |
| Hemanth Kumar | 2023-02-17 07:38:22 UTC | Flags | needinfo?(mchangir) | |
| Greg Farnum | 2023-03-23 14:14:15 UTC | Flags | needinfo?(vshankar) | |
| CC | gfarnum, vshankar | |||
| Milind Changire | 2023-03-23 15:28:23 UTC | Flags | needinfo?(mchangir) | |
| Venky Shankar | 2023-03-23 16:13:28 UTC | Assignee | vshankar | mchangir |
| Venky Shankar | 2023-03-28 06:33:53 UTC | Flags | needinfo?(vshankar) | |
| Milind Changire | 2023-04-10 09:28:22 UTC | Status | NEW | POST |
| Greg Farnum | 2023-04-10 15:12:02 UTC | Status | POST | MODIFIED |
| Keywords | Rebase | |||
| errata-xmlrpc | 2023-04-10 21:38:35 UTC | Status | MODIFIED | ON_QA |
| Hemanth Kumar | 2023-04-24 19:28:13 UTC | Flags | needinfo?(mchangir) | |
| Milind Changire | 2023-04-26 01:41:38 UTC | CC | hyelloji | |
| Flags | needinfo?(hyelloji) | |||
| Milind Changire | 2023-04-26 02:53:49 UTC | Flags | needinfo?(mchangir) | |
| Hemanth Kumar | 2023-04-26 07:54:24 UTC | Status | ON_QA | VERIFIED |
| Hemanth Kumar | 2023-04-29 10:09:06 UTC | Flags | needinfo?(hyelloji) | needinfo- |
| Akash Raj | 2023-05-03 06:34:45 UTC | CC | akraj | |
| Flags | needinfo?(mchangir) | |||
| Docs Contact | akraj | |||
| Milind Changire | 2023-05-03 08:16:40 UTC | Doc Text | Cause: The pool-level snaps and mon-managed snaps have their own snap ID namespace and this causes a clash of IDs and the mon is unable to uniquely identify a snap i.e. whether it is a pool-level snap or a mon-managed snap. Consequence: The wrong snap might get deleted when referring to an ID which is present in the set of pool-level snaps and in the set of mon-managed snaps. Fix: The fix is to disable pool-level snaps for pools attached to a cephfs filesystem. Result: When pool-level snaps are disabled for pools attached to a cephfs instance, there is no clash of pool IDs and hence no unintentional data loss in case a cephfs snap is removed. | |
| Doc Type | If docs needed, set a value | Bug Fix | ||
| Akash Raj | 2023-05-08 02:42:21 UTC | Blocks | 2192813 | |
| Milind Changire | 2023-05-16 02:52:36 UTC | Flags | needinfo?(mchangir) | |
| Doc Text | Cause: The pool-level snaps and mon-managed snaps have their own snap ID namespace and this causes a clash of IDs and the mon is unable to uniquely identify a snap i.e. whether it is a pool-level snap or a mon-managed snap. Consequence: The wrong snap might get deleted when referring to an ID which is present in the set of pool-level snaps and in the set of mon-managed snaps. Fix: The fix is to disable pool-level snaps for pools attached to a cephfs filesystem. Result: When pool-level snaps are disabled for pools attached to a cephfs instance, there is no clash of pool IDs and hence no unintentional data loss in case a cephfs snap is removed. | Cause: The pool-level snaps and fs-level snaps have their own snap ID namespace and this causes a clash of IDs and the mon is unable to uniquely identify a snap i.e. whether it is a pool-level snap or a fs-level snap. Consequence: The wrong snap might get deleted when referring to an ID which is present in the set of pool-level snaps and in the set of fs-level snaps. Fix: The fix is to disable pool-level snaps for pools attached to a cephfs filesystem. Result: When pool-level snaps are disabled for pools attached to a cephfs instance, there is no clash of pool IDs and hence no unintentional data loss in case a fs-level snap is removed. |
||
| Akash Raj | 2023-05-16 04:09:02 UTC | Doc Text | Cause: The pool-level snaps and fs-level snaps have their own snap ID namespace and this causes a clash of IDs and the mon is unable to uniquely identify a snap i.e. whether it is a pool-level snap or a fs-level snap. Consequence: The wrong snap might get deleted when referring to an ID which is present in the set of pool-level snaps and in the set of fs-level snaps. Fix: The fix is to disable pool-level snaps for pools attached to a cephfs filesystem. Result: When pool-level snaps are disabled for pools attached to a cephfs instance, there is no clash of pool IDs and hence no unintentional data loss in case a fs-level snap is removed. | .Pool-level snaps for pools attached to a Ceph File System are disabled Previously, the pool-level snaps and mon-managed snaps had their own snap ID namespace and this caused a clash between the IDs, and the Ceph Monitor was unable to uniquely identify a snap as to whether it is a pool-level snap or a mon-managed snap. Due to this, there were chances for the wrong snap to get deleted when referring to an ID, which is present in the set of pool-level snaps and mon-managed snaps. With this fix, the pool-level snaps for the pools attached to a Ceph File System are disabled and no clash of pool IDs occurs. Hence, no unintentional data loss happens when a CephFS snap is removed. |
| Milind Changire | 2023-05-16 07:36:19 UTC | Flags | needinfo?(akraj) | |
| errata-xmlrpc | 2023-06-15 09:08:23 UTC | Status | VERIFIED | RELEASE_PENDING |
| errata-xmlrpc | 2023-06-15 09:16:51 UTC | Status | RELEASE_PENDING | CLOSED |
| Resolution | --- | ERRATA | ||
| Last Closed | 2023-06-15 09:16:51 UTC |
Back to bug 2168541