-
Notifications
You must be signed in to change notification settings - Fork 421
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
Yet another Systemd Timer activation issue (edge case) #627
Comments
From #613
@nathwill don't you think we should enable the
|
@tas50 We may need your input here ^. |
@Annih We've recently made some changes in cookbook for Systemd Timer, Could you please check and confirm if issue is still there? |
Cookbook version
11.2.0
Chef-client version
12.18.31 (old one sorry, but I'm sure it is reproducible with >= 14)
Platform Details
CentOS 7.4
Scenario:
Reboot a server after system upgrades and have Chef-client still running every X minutes - when configured as timer.
Steps to Reproduce:
This is a rare edge case, I didn't manage to reproduce it on demand. I suspect a race condition blocking the activation of the
chef-client.service
at boot time.Expected Result:
Chef runs every X minutes.
Actual Result:
Chef never runs.
Timer is in weird state:
The text was updated successfully, but these errors were encountered: