Back to bug 2102934

Who When What Removed Added
Red Hat One Jira (issues.redhat.com) 2022-07-01 03:27:13 UTC Link ID Red Hat Issue Tracker RHCEPH-4653
Venky Shankar 2022-07-05 12:28:54 UTC Status NEW ASSIGNED
Assignee vshankar mchangir
Milind Changire 2022-08-26 13:08:00 UTC Target Release 6.1 5.3z1
Venky Shankar 2022-09-01 05:54:09 UTC CC vshankar
Vikhyat Umrao 2022-09-07 22:23:09 UTC CC tserlin
Target Release 5.3z1 5.3
CC vumrao
Scott Ostapovicz 2022-09-08 13:00:14 UTC CC sostapov
Target Release 5.3 5.3z1
Vikhyat Umrao 2022-09-08 15:16:05 UTC CC mhackett
Flags needinfo?(mhackett)
Greg Farnum 2022-09-09 01:38:02 UTC CC gfarnum, mchangir
Flags needinfo?(mchangir) needinfo?(vshankar)
Target Release 5.3z1 5.3
Milind Changire 2022-09-09 10:00:49 UTC Flags needinfo?(mchangir)
Venky Shankar 2022-09-09 12:11:47 UTC Flags needinfo?(vshankar)
Venky Shankar 2022-09-09 14:56:22 UTC Status ASSIGNED POST
errata-xmlrpc 2022-09-09 18:04:44 UTC Fixed In Version ceph-16.2.10-40.el8cp
Status POST MODIFIED
Status MODIFIED ON_QA
Lijo Stephen Thomas 2022-09-14 07:24:41 UTC Blocks 2125773
CC lithomas
Veera Raghava Reddy 2022-09-18 18:41:33 UTC QA Contact hyelloji julpark
CC vereddy
Veera Raghava Reddy 2022-09-19 19:33:40 UTC Assignee mchangir julpark
Target Release 5.3 6.0
Assignee julpark mchangir
Target Release 6.0 5.3
Akash Raj 2022-12-14 07:29:45 UTC Flags needinfo?(mchangir)
Status ON_QA VERIFIED
Docs Contact akraj
Flags needinfo?(mchangir)
CC akraj
Milind Changire 2022-12-19 09:31:26 UTC Doc Type If docs needed, set a value Bug Fix
Flags needinfo?(mhackett) needinfo?(mchangir) needinfo?(mchangir)
Doc Text Cause: In-memory database wasn't being written to persistent storage on every change to the schedules.

Consequence: This caused changes to snap-schedules to get lost on mgr restart.

Fix: The fix was to dump the in-memory db to persistent storage on every change or addition to the snap-schedules.

Result: Retention should continue to work across mgr restarts.
Akash Raj 2022-12-26 04:56:48 UTC Doc Text Cause: In-memory database wasn't being written to persistent storage on every change to the schedules.

Consequence: This caused changes to snap-schedules to get lost on mgr restart.

Fix: The fix was to dump the in-memory db to persistent storage on every change or addition to the snap-schedules.

Result: Retention should continue to work across mgr restarts.
.`snap-schedules` are no longer lost on restarts of Ceph Manager services

Previously, in-memory databases were not written to persistent storage on every change to the schedule. This caused `snap-schedules` to get lost on restart of Ceph Manager services.

With this fix, the in-memory databases are dumped into persistent storage on every change or addition to the `snap-schedules`. Retention now continues to work across restarts of Ceph Manager services.
Blocks 2126049
Akash Raj 2022-12-26 05:04:18 UTC Flags needinfo?(mchangir)
Red Hat Bugzilla 2023-01-01 05:39:37 UTC CC tserlin
Red Hat Bugzilla 2023-01-01 05:52:27 UTC CC mhackett
Red Hat Bugzilla 2023-01-01 08:30:48 UTC QA Contact julpark
Red Hat Bugzilla 2023-01-01 08:42:41 UTC CC sostapov
Red Hat Bugzilla 2023-01-01 08:47:17 UTC CC vereddy
Red Hat Bugzilla 2023-01-01 08:49:28 UTC CC vshankar
Red Hat Bugzilla 2023-01-01 08:49:53 UTC CC vumrao
Milind Changire 2023-01-03 07:55:13 UTC Flags needinfo?(mchangir)
Alasdair Kergon 2023-01-04 04:39:42 UTC QA Contact julpark
Alasdair Kergon 2023-01-04 05:43:50 UTC CC sostapov
Alasdair Kergon 2023-01-04 05:57:59 UTC CC vshankar
Alasdair Kergon 2023-01-04 05:59:30 UTC CC vumrao
Alasdair Kergon 2023-01-04 06:25:53 UTC CC tserlin
Alasdair Kergon 2023-01-04 06:59:12 UTC CC vereddy
Alasdair Kergon 2023-01-04 11:29:24 UTC CC mhackett
Red Hat Bugzilla 2023-01-09 08:28:09 UTC CC ceph-eng-bugs
Alasdair Kergon 2023-01-09 19:43:36 UTC CC ceph-eng-bugs
errata-xmlrpc 2023-01-11 17:39:52 UTC Resolution --- ERRATA
Status VERIFIED CLOSED
Last Closed 2023-01-11 17:39:52 UTC
errata-xmlrpc 2023-01-11 17:40:48 UTC Link ID Red Hat Product Errata RHSA-2023:0076
Hemanth Kumar 2023-07-04 14:41:53 UTC CC hyelloji

Back to bug 2102934