Back to bug 2216186
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| Red Hat One Jira (issues.redhat.com) | 2023-06-20 11:56:53 UTC | Link ID | Red Hat Issue Tracker RHCEPH-6891 | |
| Ilya Dryomov | 2023-07-10 19:23:22 UTC | Severity | high | urgent |
| Ilya Dryomov | 2023-07-10 20:49:13 UTC | Status | ASSIGNED | POST |
| Manasa | 2023-07-11 05:18:51 UTC | Fixed In Version | ceph-17.2.6-84.el9cp | |
| CC | mgowri, tserlin, vereddy | |||
| Status | POST | MODIFIED | ||
| Flags | needinfo?(mgowri) | |||
| Flags | needinfo?(vereddy) | |||
| Flags | needinfo?(mgowri) needinfo?(vereddy) | needinfo+ needinfo+ | ||
| errata-xmlrpc | 2023-07-11 05:27:12 UTC | Status | MODIFIED | ON_QA |
| Ilya Dryomov | 2023-07-11 09:39:36 UTC | Flags | needinfo+ needinfo+ | |
| Akash Raj | 2023-07-13 17:51:36 UTC | Flags | needinfo?(idryomov) | |
| Blocks | 2221020 | |||
| CC | akraj | |||
| Docs Contact | akraj | |||
| Ilya Dryomov | 2023-07-19 12:32:29 UTC | Doc Type | If docs needed, set a value | Bug Fix |
| Doc Text | Cause: Previously, due to an implementation defect, an stale snapshot context could be used when handling a write(-like) operation. Consequence: The object map for the snapshot wasn't guaranteed to accurately reflect the contents of the snapshot in case the snapshot was taken without quiescing the workload. In differential backup and snapshot-based mirroring use cases with object-map and/or fast-diff features enabled, the destination image could get corrupted. Fix: The implementation defect was fixed. Result: The object map for the snapshot should accurately reflect the contents of the snapshot even in case the snapshot is taken without quiescing the workload. In differential backup and snapshot-based mirroring use cases with object-map and/or fast-diff features enabled, the destination image doesn't get corrupted. | |||
| Flags | needinfo?(idryomov) | |||
| Ilya Dryomov | 2023-07-19 12:34:39 UTC | Doc Text | Cause: Previously, due to an implementation defect, an stale snapshot context could be used when handling a write(-like) operation. Consequence: The object map for the snapshot wasn't guaranteed to accurately reflect the contents of the snapshot in case the snapshot was taken without quiescing the workload. In differential backup and snapshot-based mirroring use cases with object-map and/or fast-diff features enabled, the destination image could get corrupted. Fix: The implementation defect was fixed. Result: The object map for the snapshot should accurately reflect the contents of the snapshot even in case the snapshot is taken without quiescing the workload. In differential backup and snapshot-based mirroring use cases with object-map and/or fast-diff features enabled, the destination image doesn't get corrupted. | Cause: Previously, due to an implementation defect, a stale snapshot context could be used when handling a write(-like) operation. Consequence: The object map for the snapshot wasn't guaranteed to accurately reflect the contents of the snapshot in case the snapshot was taken without quiescing the workload. In differential backup and snapshot-based mirroring use cases with object-map and/or fast-diff features enabled, the destination image could get corrupted. Fix: The implementation defect was fixed. Result: The object map for the snapshot should accurately reflect the contents of the snapshot even in case the snapshot is taken without quiescing the workload. In differential backup and snapshot-based mirroring use cases with object-map and/or fast-diff features enabled, the destination image doesn't get corrupted. |
| Manasa | 2023-07-24 07:05:10 UTC | Status | ON_QA | VERIFIED |
| Akash Raj | 2023-07-25 04:30:24 UTC | Doc Text | Cause: Previously, due to an implementation defect, a stale snapshot context could be used when handling a write(-like) operation. Consequence: The object map for the snapshot wasn't guaranteed to accurately reflect the contents of the snapshot in case the snapshot was taken without quiescing the workload. In differential backup and snapshot-based mirroring use cases with object-map and/or fast-diff features enabled, the destination image could get corrupted. Fix: The implementation defect was fixed. Result: The object map for the snapshot should accurately reflect the contents of the snapshot even in case the snapshot is taken without quiescing the workload. In differential backup and snapshot-based mirroring use cases with object-map and/or fast-diff features enabled, the destination image doesn't get corrupted. | .Object map for the snapshot accurately reflects the contents of the snapshot Previously, due to an implementation defect, a stale snapshot context would be used when handling a write-like operation. Due to this, the object map for the snapshot was not guaranteed to accurately reflect the contents of the snapshot in case the snapshot was taken without quiescing the workload. In differential backup and snapshot-based mirroring, use cases with object-map and/or fast-diff features enabled, the destination image could get corrupted. With this fix, the implementation defect is fixed and everything works as expected. |
| Red Hat Bugzilla | 2023-08-03 08:30:07 UTC | CC | ocs-bugs | |
| errata-xmlrpc | 2023-08-03 16:32:36 UTC | Status | VERIFIED | RELEASE_PENDING |
| errata-xmlrpc | 2023-08-03 16:45:10 UTC | Resolution | --- | ERRATA |
| Status | RELEASE_PENDING | CLOSED | ||
| Last Closed | 2023-08-03 16:45:10 UTC | |||
| errata-xmlrpc | 2023-08-03 16:46:03 UTC | Link ID | Red Hat Product Errata RHBA-2023:4473 |
Back to bug 2216186