-
Notifications
You must be signed in to change notification settings - Fork 8
(RHEL-118216) timer: don't run service immediately after restart of a timer #90
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
(RHEL-118216) timer: don't run service immediately after restart of a timer #90
Conversation
Commit validationTracker - RHEL-118216 The following commits meet all requirements
Tracker validationSuccess🟢 Tracker RHEL-118216 has set desired product: Pull Request validationSuccess🟡 CI - Waived Auto MergeSuccess🟢 Pull Request is not marked as draft and it's not blocked by |
And split the existing test into a separate subtest. (cherry picked from commit 953c347fb6f293acbd6da009646bfc071b68ddd7) Related: RHEL-118216
…rvice Provides coverage for: - systemd/systemd#31231 - systemd/systemd#35805 (cherry picked from commit 5730a400fd5ee82566fe03eb832121a0d4bc26b6) Related: RHEL-118216
When deserializing a serialized timer unit with RandomizedDelaySec= set, systemd should use the last inactive exit timestamp instead of current realtime to calculate the new next elapse, so the timer unit actually runs in the given calendar window. Provides coverage for: - systemd/systemd#18678 - systemd/systemd#27752 (cherry picked from commit f4c3c107d9be4e922a080fc292ed3889c4e0f4a5) Related: RHEL-118216
When a timer is restarted, don't reset the last_trigger field. This prevents the timer from triggering immediately. Fixes: #31231 (cherry picked from commit 3fc44a0f68412b649e16f12ff2f97a36c615457d) Resolves: RHEL-118216
Follow-up for 5730a400fd5ee82566fe03eb832121a0d4bc26b6. (cherry picked from commit 0cb252d50f35256bff569fa6213784f2d45ad6a1) Related: RHEL-118216
6993f37 to
ffe8e95
Compare
|
The CI fails are unrelated (libasan errors), but I'll look into them soon. |
dtardon
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
c2a0cd9
into
redhat-plumbers:main
When a timer is restarted, don't reset the last_trigger field.
This prevents the timer from triggering immediately.
Fixes: #31231
(cherry picked from commit 3fc44a0f68412b649e16f12ff2f97a36c615457d)
Resolves: RHEL-118216