Back to bug 2181055
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| Red Hat One Jira (issues.redhat.com) | 2023-03-23 00:15:47 UTC | Link ID | Red Hat Issue Tracker RHCEPH-6292 | |
| Josh Durgin | 2023-03-23 00:22:06 UTC | Assignee | idryomov | prasanna.kalever |
| Status | NEW | ASSIGNED | ||
| Target Release | 6.1z1 | 6.1 | ||
| Shyamsundar | 2023-03-23 13:53:55 UTC | CC | srangana | |
| Veera Raghava Reddy | 2023-04-16 09:20:10 UTC | CC | vereddy | |
| Ilya Dryomov | 2023-04-19 15:47:00 UTC | Link ID | Ceph Project Bug Tracker 59393 | |
| CC | idryomov | |||
| Assignee | prasanna.kalever | choffman | ||
| Ilya Dryomov | 2023-05-10 16:41:50 UTC | Status | ASSIGNED | POST |
| errata-xmlrpc | 2023-05-10 20:01:40 UTC | CC | tserlin | |
| Status | POST | MODIFIED | ||
| Fixed In Version | ceph-17.2.6-46.el9cp | |||
| Status | MODIFIED | ON_QA | ||
| Vasishta | 2023-06-06 08:22:21 UTC | Flags | needinfo?(jdurgin) | |
| Ilya Dryomov | 2023-06-06 08:59:45 UTC | CC | vashastr | |
| Flags | needinfo?(vashastr) | |||
| Vasishta | 2023-06-06 09:03:59 UTC | Dependent Products | Red Hat OpenShift Data Foundation | |
| Vasishta | 2023-06-06 09:13:57 UTC | Flags | needinfo?(vashastr) | |
| Dependent Products | Red Hat OpenShift Data Foundation | |||
| Vasishta | 2023-06-07 15:02:07 UTC | Status | ON_QA | VERIFIED |
| Vasishta | 2023-06-07 15:06:33 UTC | Blocks | 2213237 | |
| Vasishta | 2023-06-08 04:25:39 UTC | Flags | needinfo?(jdurgin) | |
| Ilya Dryomov | 2023-06-13 10:54:10 UTC | Blocks | 2192813 | |
| Christopher Hoffman | 2023-06-14 14:20:59 UTC | Doc Text | Cause: Remote cluster cannot grab lock quickly enough to remove synced snapshot while I/O is underway. This can be due to latency between sites. Consequence: The mirror image snapshot sync process gets stuck on the removal snapshot step and does not continue with syncing further snapshots. Fix: Move snapshot removal step to primary site which can grab lock fast enough to remove snapshot. Result: The mirror image snapshot sync doesn't get stuck and continues as normal. | |
| Doc Type | If docs needed, set a value | Bug Fix | ||
| errata-xmlrpc | 2023-06-15 09:08:26 UTC | Status | VERIFIED | RELEASE_PENDING |
| errata-xmlrpc | 2023-06-15 09:16:51 UTC | Resolution | --- | ERRATA |
| Status | RELEASE_PENDING | CLOSED | ||
| Last Closed | 2023-06-15 09:16:51 UTC | |||
| Akash Raj | 2023-06-21 09:19:28 UTC | CC | akraj | |
| Doc Text | Cause: Remote cluster cannot grab lock quickly enough to remove synced snapshot while I/O is underway. This can be due to latency between sites. Consequence: The mirror image snapshot sync process gets stuck on the removal snapshot step and does not continue with syncing further snapshots. Fix: Move snapshot removal step to primary site which can grab lock fast enough to remove snapshot. Result: The mirror image snapshot sync doesn't get stuck and continues as normal. | .Snapshot removal tep is moved to the primary site Previously, a remote cluster could not grab lock quickly enough to remove synced snapshot while I/O was underway due to latency between sites. This would cause the mirror image snapshot sync process to be stuck during snapshot removal and would not continue with syncing further snapshots. With this fix, the snapshot removal step is moved to the primary site which grabs the lock fast enough to remove the snapshot and the mirror image snapshot sync does not get stuck and works as expected. |
Back to bug 2181055