-
Notifications
You must be signed in to change notification settings - Fork 46
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
OL8.10: systemd user timers fire inappropriately #171
Comments
Oracle Linux customers, please file your issue at https://support.oracle.com Thanks for filing an issue with Oracle Linux. GitHub Issues is not an official support channel and we don't offer Even if you're not a customer, if we can confirm that an issue is a |
Hi @YoderExMachina, The old Bugzilla reporting site directed me here. For clarity, are you saying this bug report has been received and entered into your internal system, and you'll post updates here (in this closed card) as resolutions are identified? |
Yes, "Even if you're not a customer, if we can confirm that an issue is a bug we will do our best to fix it and to update this issue once it has been fixed." |
A regression in systemd has been introduced between OL8.8 and OL8.10, the two versions I have available to test.
Background
We keep a service user's systemd configuration in a repository and publish it to machines upon changes. Pre- and post-publishing scripts run to refresh systemd's state to ensure added services are started and removed services are stopped. A single target unit references all other units, most of which are timers.
Expected behavior
Stopping and restarting the target should reload any timers. The timers should fire as scheduled.
Actual behavior
If the timers have ever run before, upon restarting the target, all configured timers run immediately.
Versions
Not impacted:
systemd 239-74.0.4.el8_8.3
Impacted:
systemd 239-82.0.2.el8_10.3
Minimal Repro
Workaround
Disabling the target before stopping it, and then reenabling it before starting avoids the unexpected behavior.
The text was updated successfully, but these errors were encountered: