related to #305 run fails if system does not have systemd fact

[vchan2002]

It would appear that, with #305, does not work on systems that does not have the systemd fact.

A workaround we did for now is creating a fact called systemd on our own....

Is that fact supposed to be set somewhere using this, or some other puppet module?

Error: Could not retrieve catalog from remote server: Error 400 on SERVER: str2bool(): Wrong number of arguments given (0 for 1) at /etc/puppet/envs/staging/modules/zabbix/manifests/agent.pp:331 on node -----
Warning: Not using cache on failed catalog
Error: Could not retrieve catalog; skipping run

Affected Puppet, Ruby, OS and module versions/distributions

• Puppet: 3.7.5
• Ruby: 2.0.0
• Distribution: Amazon Linux
• Module version: 2.6

How to reproduce (e.g Puppet code you use)

What are you seeing

What behaviour did you expect instead

Output log

Any additional information you'd like to impart

[gyoza]

I can confirm this is accurate and true. I have experienced this myself.

[vchan2002]

NM... I see the dependency to the systemd module that provides the fact....

[tdac]

Hi - I'm still seeing this on buntu 14.04.5 despite having camptocamp/systemd on the puppetmaster. Can anyone give me a steer as to how to resolve this issue?

[AHPyXA]

Faced the same issue.

Notice: Module camptocamp-systemd 0.4.0 is already installed.

Is it may be puppet/facter version related?
OS - ubuntu 14.04
With puppet 3.4.3 and facter 1.7.5 from ubuntu repo I got the problem
With puppet 3.8.7 and facter 2.4.6 from puppetlabs the problem is gone

[bastelfreak]

Hi @AHPyXA,

We don't support facter 1.X and puppet 3.X anymore. Facter 1.X doesn't support the used hash syntax, also there are multiple puppet4 types used. Puppet3 is end of life since January, everybody should really upgrade. Feel free to join our IRC channel #voxpupuli on freenode if you've any questions about upgrading puppet.