-
-
Notifications
You must be signed in to change notification settings - Fork 150
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
AppArmor is restarted after ntpd #177
Comments
|
|
joe4dev
added a commit
to sealuzh/cwb-chef-repo
that referenced
this issue
Jun 28, 2020
An issue with the ntp recipe breaks the Ubuntu 16.04 build: ``` Ran /bin/systemctl --system restart apparmor returned 1 ``` See https://travis-ci.org/github/sealuzh/cwb-chef-repo/builds/702873714 Maybe related to sous-chefs/ntp#177
Marking stale due to inactivity. Remove stale label or comment or this will be closed in 7 days. Alternatively drop by the #sous-chefs channel on the Chef Community Slack and we'll be happy to help! Thanks, Sous-Chefs. |
github-actions
bot
added
the
Stale
This is marked as stale and will be closed shortly
label
Jan 8, 2021
Is this problem fixed in newer ubuntu versions? |
github-actions
bot
removed
the
Stale
This is marked as stale and will be closed shortly
label
Jan 9, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Cookbook version
3.5.4, had the same issue with 3.3.1
Chef-client version
12.18.31
Platform Details
Ubuntu 16.04
ntp::apparmor issues a notify to AppArmor after creating the usr.sbin.ntpd profile. I'm not sure if this happens during each run, but sometimes the restart for AppArmor happens after NTP.
This causes issues with (at least) the /etc/ntp.leapseconds file.
After restarting NTP by hand on the converged node, it reads the file normally.
The text was updated successfully, but these errors were encountered: