Bug 2255938
Summary: | [Tracker #63613]: Using custom lc schedule (work time) may cause lc processing to stall. | |||
---|---|---|---|---|
Product: | [Red Hat Storage] Red Hat Ceph Storage | Reporter: | Manny <mcaldeir> | |
Component: | RGW | Assignee: | Matt Benjamin (redhat) <mbenjamin> | |
Status: | CLOSED ERRATA | QA Contact: | Chaithra <ckulal> | |
Severity: | medium | Docs Contact: | ||
Priority: | unspecified | |||
Version: | 6.1 | CC: | akraj, ceph-eng-bugs, cephqe-warriors, ckulal, mcaldeir, tserlin | |
Target Milestone: | --- | |||
Target Release: | 7.1 | |||
Hardware: | Unspecified | |||
OS: | Unspecified | |||
Whiteboard: | ||||
Fixed In Version: | ceph-18.2.1-96.el9cp | Doc Type: | Bug Fix | |
Doc Text: |
.The work scheduler now takes the next date into account in the `should_work` function
Previously, the logic used in the `should_work` function, that decides whether the lifecycle should start running at the current time, would not take the next date notion into account. As a result, any custom work time "XY:TW-AB:CD" would break the lifecycle processing when AB < XY.
With this fix, the work scheduler now takes the next date into account and the various custom lifecycle work schedules now function as expected.
|
Story Points: | --- | |
Clone Of: | ||||
: | 2255939 (view as bug list) | Environment: | ||
Last Closed: | 2024-06-13 14:24:01 UTC | Type: | Bug | |
Regression: | --- | Mount Type: | --- | |
Documentation: | --- | CRM: | ||
Verified Versions: | Category: | --- | ||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | ||
Cloudforms Team: | --- | Target Upstream Version: | ||
Embargoed: | ||||
Bug Depends On: | ||||
Bug Blocks: | 2255939 |
Description
Manny
2023-12-26 23:09:41 UTC
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (Critical: Red Hat Ceph Storage 7.1 security, enhancements, and bug fix update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2024:3925 |