Skip to content

Conversation

@bastelfreak
Copy link
Member

Two changes: With adding network-online.target as dependency we ensure
that the network is really available. That might not be the case for the
network.target. In case the system has no proper network manager,
network-online.target isn't available. For that situation we still
depend on network.target. Also we now have Wants= defined. That will
start the targets if the agent is started.

We had a similar discussion upstream:
puppetlabs/puppet#8893

Two changes: With adding network-online.target as dependency we ensure
that the network is really available. That might not be the case for the
network.target. In case the system has no proper network manager,
network-online.target isn't available. For that situation we still
depend on network.target. Also we now have Wants= defined. That will
start the targets if the agent is started.

We had a similar discussion upstream:
puppetlabs/puppet#8893
@ekohl
Copy link
Member

ekohl commented Mar 16, 2022

I wonder if we should push the timer upstream.

@evgeni
Copy link
Member

evgeni commented Apr 19, 2022

I'm wondering why the Wants change -- you don't have the same in the linked puppet.service PR.

My biggest "fear" (hard word) here is: a user has intentionally dropped out of network target, but because the timer is active, it will turn the network back on again? Feels like this is something we should have no business in. Or am I misunderstanding timers (possible).

@evgeni
Copy link
Member

evgeni commented Apr 19, 2022

(depending on the discussion, we could squeeze that in into #834 ;))

@ekohl
Copy link
Member

ekohl commented Jan 13, 2023

@bastelfreak since you linked the PR to me, any idea about what @evgeni said?

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.

4 participants