do you have anything that provides

network-online.target

? If your agen't doesn't set that in

After=

in it's systemd unit, add that

Yup, we have network-online.target and puppet agent service has been configured to wait for it.

# /lib/systemd/system/puppet.service
#
# Local settings can be configured without being overwritten by package upgrades, for example
# if you want to increase puppet open-files-limit to 10000,
# you need to increase systemd's LimitNOFILE setting, so create a file named
# "/etc/systemd/system/puppet.service.d/limits.conf" containing:
# [Service]
# LimitNOFILE=10000
# You can confirm it worked by running systemctl daemon-reload
# then running systemctl show puppet | grep LimitNOFILE
#
[Unit]
Description=Puppet agent
Wants=basic.target
After=basic.target network.target

[Service]
EnvironmentFile=-/etc/sysconfig/puppetagent
EnvironmentFile=-/etc/sysconfig/puppet
EnvironmentFile=-/etc/default/puppet
ExecStart=/opt/puppetlabs/puppet/bin/puppet agent $PUPPET_EXTRA_OPTS --no-daemonize
ExecReload=/bin/kill -HUP $MAINPID
KillMode=process

[Install]
WantedBy=multi-user.target

# /etc/systemd/system/puppet.service.d/puppet.service.conf
[Unit]
Description=Puppet agent
Wants=basic.target
After=basic.target network.target network-online.target

I've also tried adding

After=nss-lookup.target

but get the same issue

do you have

systemd-networkd-wait-online.service

and is it enabled?

We do but it's disabled. We're using NetworkManager for these devices since they're laptop/desktop machines. We do have the

NetworkManager-wait-online.service

instead though

ah okay. that should provide network-online.target as well

any unit provides name resolution for you, that you can depend on? systemd-resolvd?

or hack an execstartpre that sleeps until name resolution works

I'll give those options a go and see what happens 👍 thanks for the suggestions.

This message was deleted.

I noticed a small weird bug. I accidentally wrote the following in a manifest:

"somestring-${$variable_name}-blahblah"

and it works, despite there is typo (can you see the dollar symbol before and after the curly bracket?) It can be easily reproduced with puppet-debugger:

this is puppet 7

I believe it’s feature :) though I know @helindbe can explain it better

aah.... it's not even an unescaped special character.... if I use

^

or I put

$

at the end it throws an error. And if I use only the dollar inside the curly bracket it does not interpolate the variable. Let's wait for @helindbe

Without the $ is the special case actually (for interpolating a variable).

this is what I can see:

Yes, works as it should

${} interpolates and substitutes what is inside. That’s why it works this way (from my understanding)

Ah, so skipping $ inside is THE feature :)

and this is ignored =>

{$...

but this one fails =>

{...$

😵‍💫

The braced contents is a puppet expression, plus special case that an initial bare word is taken as the name of a variable.

🧩 I am puzzled... I take a coffee

It’s not a regular expression :) it’s puppet language expression (https://puppet.com/docs/puppet/7/lang_expressions.html).. e.g. you can write ${mylist.join(‘,’)}

Or maybe ${$a + $b}

message has been deleted

This message was deleted.

message has been deleted

This message was deleted.

This message was deleted.