Puppet Community

I would stick with systemd::timer being the actual thing that makes timers, then making systemd::timer_clock::(interfaces)

i prefer a separate defined type otherwise the interface is to confusing

where (interfaces) is a set of simplified obvious usecases

Can still be 'simple' as in this is a Type=simple service unit. Nothing to do with "simple" arguments. 

systemd::timer_clock::single   (single not simple ) ?

I spent a full day fixing my vagrant setup

because debian shipped net-ssh 7 and vagrant-hosts doesn't work with it

are you running Debian experimental or something?

but once every couple years it drops something like this on me

Hi, I was searching for this exact error and noticed you ran into the same problem I just did.   So in case you are still inconvenienced by this:  This is a Puppet Debugger problem, caused by <https://github.com/puppetlabs/bolt/pull/3092|this Bolt PR> (released in 3.23.0).  That patch rearranged the API for the `Bolt::PuppetDB::Config` class, including removing the `load_config` method.

I just submitted a PR to fix it at <https://github.com/nwops/puppet-debugger/pull/74>

Wow! Thank you for the update! I didn’t tried it after though :)

So, I just ran into this. Does anyone know what would be the process to get my pdk to pull in the updated version of puppet-debugger?

pdk usually includes all of its dependencies, so you'd likely be waiting for the next version of pdk to drop that will include the fix

`pdk bundle update` works to pull in latest dependencies that a Gemfile allows

HUZZAH! That fixed it! Thanks <@U1PC2RAH0> +++ and <@U11LKL4S2> +++

bastelfreak gained a level! (Karma: 26)
op-ct +1! (Karma: 3)

Can I get a review of <https://github.com/voxpupuli/puppet-chrony/pull/151>

.... that is odd, as that is what RHEL is defaulting to

<http://kenta.blogspot.com/2016/03/sqfzcxay-understanding-right-time-zone.html>

that seems like right/UTC is a bad default, unless RHEL has a very good reason for it

I'll confess I have no idea why that is their default, but figured the puppet defaults should probably match the vendor defaults

```[root@rhel9-dev ~]# ls -l /usr/share/zoneinfo/right/UTC 
-rw-r--r-- 8 root root 664 Mar 21 14:30 /usr/share/zoneinfo/right/UTC
[root@rhel9-dev ~]# ls -l /usr/share/zoneinfo/right/Etc/UTC
-rw-r--r-- 8 root root 664 Mar 21 14:30 /usr/share/zoneinfo/right/Etc/UTC```

per the link above, the right folder in tzinfo is a set of translations of UTC time to a clock not being adjusted for leap seconds

so maybe their chrony configuration ignores leap seconds at the ntp level and adjusts at the tz level?

Since it is the `leaptz` setting maybe it is using that to detect leapseconds?

that looks to be exactly it, <https://chrony.tuxfamily.org/doc/2.1/manual.html#leapsectz-directive>