Skip to content
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

run Puppet agent from systemd only after network is brought up #765

Merged
merged 1 commit into from
Nov 2, 2020

Conversation

anarcat
Copy link
Contributor

@anarcat anarcat commented Sep 21, 2020

Using After ensures proper ordering between the Puppet service and
the machine's networking. We could also have used Wants or
Requires but, according to the systemd.unit(5) manpage, After
only ensure ordering, while Wants and Requires
actually trigger units.

In other words, After ensures that puppet-run will be started
after networking is up, but will not necessarily run when networking
is up, nor will it attempt to bring up networking when ran.

Closes: #764

Using `After` ensures proper ordering between the Puppet service and
the machine's networking. We could also have used `Wants` or
`Requires` but, according to the `systemd.unit(5)` manpage, `After`
only ensure *ordering*, while `Wants` and `Requires`
actually *trigger* units.

In other words, `After` ensures that `puppet-run` will be started
after networking is up, but will not *necessarily* run when networking
is up, nor will it attempt to bring up networking when ran.

Closes: theforeman#764
@ekohl ekohl merged commit 5bf8035 into theforeman:master Nov 2, 2020
@anarcat anarcat deleted the service-dep branch November 8, 2020 18:25
@ekohl ekohl added the Bug label Jan 25, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

systemd timer service should depend on networking
3 participants