Back to bug 2072680

Who When What Removed Added
RHEL Program Management 2022-04-06 18:34:01 UTC Keywords FutureFeature
Matt Benjamin (redhat) 2022-04-06 18:53:04 UTC Status NEW ASSIGNED
Red Hat One Jira (issues.redhat.com) 2022-04-06 19:13:13 UTC Link ID Red Hat Issue Tracker RHCEPH-3933
Justin Bautista 2022-04-06 20:14:05 UTC Blocks 1725227
Veera Raghava Reddy 2022-05-10 18:46:05 UTC CC vereddy
Red Hat Bugzilla 2022-05-26 08:30:35 UTC CC ceph-qe-bugs
Red Hat Bugzilla 2023-01-01 05:42:51 UTC CC cbodley
Red Hat Bugzilla 2023-01-01 08:24:07 UTC CC kbader
Red Hat Bugzilla 2023-01-01 08:31:41 UTC CC kkeithle
Red Hat Bugzilla 2023-01-01 08:34:31 UTC Assignee mbenjamin nobody
CC mbenjamin
Red Hat Bugzilla 2023-01-01 08:36:56 UTC QA Contact mkasturi
Red Hat Bugzilla 2023-01-01 08:47:56 UTC CC vereddy
Alasdair Kergon 2023-01-04 04:44:13 UTC Assignee nobody mbenjamin
Alasdair Kergon 2023-01-04 04:58:33 UTC QA Contact mkasturi
Alasdair Kergon 2023-01-04 05:01:28 UTC CC kbader
Alasdair Kergon 2023-01-04 06:17:00 UTC CC cbodley
Alasdair Kergon 2023-01-04 06:23:48 UTC CC mbenjamin
Alasdair Kergon 2023-01-04 06:49:10 UTC CC kkeithle
Alasdair Kergon 2023-01-04 06:59:12 UTC CC vereddy
Red Hat Bugzilla 2023-01-09 08:28:42 UTC CC ceph-eng-bugs
Alasdair Kergon 2023-01-09 19:43:36 UTC CC ceph-eng-bugs
Matt Benjamin (redhat) 2023-03-26 19:07:46 UTC Status ASSIGNED MODIFIED
Ken Dreyer (Red Hat) 2023-04-03 19:57:14 UTC CC kdreyer
Keywords TestOnly
Ken Dreyer (Red Hat) 2023-04-13 21:09:13 UTC Status MODIFIED ON_QA
Chaithra 2023-04-17 06:39:38 UTC QA Contact mkasturi ckulal
CC ckulal
Chaithra 2023-04-25 10:50:13 UTC Status ON_QA ASSIGNED
Chaithra 2023-04-25 12:19:17 UTC Status ASSIGNED CLOSED
Resolution --- NOTABUG
Last Closed 2023-04-25 12:19:17 UTC
Akash Raj 2023-05-03 06:44:18 UTC Flags needinfo?(mbenjamin)
CC akraj
Docs Contact akraj
Matt Benjamin (redhat) 2023-05-03 11:44:40 UTC Doc Type If docs needed, set a value Known Issue
Doc Text Cause:
If a radosgw instance is killed (ungraceful shutdown) while lifecycle processing for one or more buckets is taking place, processing may not continue on those buckets until 2 scheduling periods have elapsed (e.g., 2 days), at which point it will be marked stale and reinitialized. This does not happen if radosgw is shutdown gracefully.

Consequence:
Lifecycle processing for some buckets might be delayed if radosgws are killed due to a crash or kill -9.

Workaround (if any):
None.

Result:
As above.
Akash Raj 2023-05-08 02:44:21 UTC Blocks 2192813
Akash Raj 2023-05-09 03:04:07 UTC Flags needinfo?(mbenjamin)
Doc Text Cause:
If a radosgw instance is killed (ungraceful shutdown) while lifecycle processing for one or more buckets is taking place, processing may not continue on those buckets until 2 scheduling periods have elapsed (e.g., 2 days), at which point it will be marked stale and reinitialized. This does not happen if radosgw is shutdown gracefully.

Consequence:
Lifecycle processing for some buckets might be delayed if radosgws are killed due to a crash or kill -9.

Workaround (if any):
None.

Result:
As above.
.Bucket lifecycle processing might get delayed if the Ceph Object Gateway instances are killed due to a crash or kill

Presently, if a Ceph Object Gateway instance is killed (ungraceful shutdown) due to a crash or kill -9 while lifecycle processing for one or more buckets is taking place, processing might not continue on those buckets until two scheduling periods have elapsed, for example, two days. At this point, the buckets are marked stale and reinitialized. There is no workaround for this issue.

Back to bug 2072680