When using Cobbler as Puppet's External Node Classifier, the Kictstart Metadata parameters configured in Cobbler override those derived from Puppet (e.g. using facts). Cobbler Metadata example [root@cobblerserver ~]# cobbler distro report --name=centos7.4-x86_64 | grep Metadata Kickstart Metadata : {'operatingsystemrelease': '7.2.1511'…
The error details [root@mynode ~]# /opt/puppetlabs/bin/puppet agent -t --server puppet_master.mycompany.com --environment production Warning: Unable to fetch my node definition, but the agent run will continue: Warning: Find /puppet/v3/node/?environment=production&configured_environment=produc... resulted in 404 with the message: Not Found:…
When applying changes to /etc/systemd/system.conf, using the systemd.lns augeas lens, I needed to change the CPU Affinity parameter. using the puppetforge systemd module, I wanted to set YAML to set the line CPUAffinity=0 1 2 3 in /etc/systemd/system.conf I already discovered through…
The below puppet error occurred. Despite the usual unhelpful reference to a ruby script, it turned out that the Puppet V3 client had been automatically uninstalled and replaced by puppet-agent. Normally, you can easily force certain versions of a particular package, however in this situation, PuppetLabs have reverted to earlier…
The problem If, when running puppet, you see the following error, it is probably not directly a fault with the init.pp file it mentions in the error code, rather a problem with a hiera lookup referenced in that line (thus in this case a problem parsing YAML). Error: Could…