Back to bug 2019909

Who When What Removed Added
Red Hat One Jira (issues.redhat.com) 2021-11-03 15:43:43 UTC Link ID Red Hat Issue Tracker RHCEPH-2166
Gopi 2022-03-11 04:32:13 UTC CC gpatta
Veera Raghava Reddy 2022-05-11 15:22:54 UTC CC vereddy
Ilya Dryomov 2022-05-18 15:17:45 UTC Flags needinfo?(vashastr)
Vasishta 2022-05-19 15:10:40 UTC Flags needinfo?(vashastr)
Ilya Dryomov 2022-05-19 15:18:04 UTC Assignee idryomov sunkumar
Target Release 5.2 6.1
Status NEW ASSIGNED
Ilya Dryomov 2022-05-19 15:18:26 UTC CC idryomov
Red Hat Bugzilla 2022-05-26 08:30:25 UTC CC ceph-qe-bugs
Ilya Dryomov 2022-06-23 09:50:22 UTC Assignee sunkumar idryomov
Target Release 6.1 5.2
Ilya Dryomov 2022-06-23 09:51:15 UTC Link ID Ceph Project Bug Tracker 56181
Ilya Dryomov 2022-06-30 14:55:58 UTC Status ASSIGNED POST
errata-xmlrpc 2022-06-30 18:07:25 UTC Fixed In Version ceph-16.2.8-65.el8cp
Status POST MODIFIED
CC tserlin
Status MODIFIED ON_QA
Gopi 2022-07-05 04:36:29 UTC Status ON_QA VERIFIED
Akash Raj 2022-07-28 09:30:16 UTC Blocks 2102272
Akash Raj 2022-07-28 09:33:02 UTC CC akraj
Flags needinfo?(idryomov)
Ilya Dryomov 2022-07-28 20:06:47 UTC Doc Text Cause:
Due to an implementation defect, last_copied_object_number value was properly updated only for fully allocated images.

Consequence:
For any sparse image, last_copied_object_number value was incorrect. In case of abrupt rbd-mirror daemon restart, this meant that image replication progress would almost certainly be lost.

Fix:
The implementation defect was fixed.

Result:
last_copied_object_number value is properly updated for all images. Upon rbd-mirror daemon restart, image replication continues exactly where it left off.
Flags needinfo?(idryomov)
Doc Type If docs needed, set a value Bug Fix
Red Hat Bugzilla 2022-07-29 18:53:06 UTC CC gpatta
Akash Raj 2022-08-03 14:42:00 UTC Doc Text Cause:
Due to an implementation defect, last_copied_object_number value was properly updated only for fully allocated images.

Consequence:
For any sparse image, last_copied_object_number value was incorrect. In case of abrupt rbd-mirror daemon restart, this meant that image replication progress would almost certainly be lost.

Fix:
The implementation defect was fixed.

Result:
last_copied_object_number value is properly updated for all images. Upon rbd-mirror daemon restart, image replication continues exactly where it left off.
.`last_copied_object_number` value is properly updated for all images

Previously, due to an implementation defect, `last_copied_object_number` value was properly updated only for fully allocated images. This caused the `last_copied_object_number` value to be incorrect for any sparse image and the image replication progress to be lost in case of abrupt rbd-mirror daemon restart.

With this fix, `last_copied_object_number` value is properly updated for all images and upon rbd-mirror daemon restart, image replication resumes from where it had previously stopped.
Flags needinfo?(idryomov)
Ilya Dryomov 2022-08-04 09:20:19 UTC Flags needinfo?(idryomov)
errata-xmlrpc 2022-08-09 09:54:45 UTC Status VERIFIED RELEASE_PENDING
errata-xmlrpc 2022-08-09 17:36:41 UTC Resolution --- ERRATA
Status RELEASE_PENDING CLOSED
Last Closed 2022-08-09 17:36:41 UTC
errata-xmlrpc 2022-08-09 17:37:12 UTC Link ID Red Hat Product Errata RHSA-2022:5997

Back to bug 2019909