The Puppet Labs Issue Tracker has Moved: https://tickets.puppetlabs.com
unhelpfull error message when parent directory is missing
|Affected Puppet version:||0.24.4||Branch:|
when creating a file, if the parent directory is missing a misleading error message is displayed, for example in the next case /etc/munin/ was missing and I tried to create /etc/munin/munin-node.conf
notice: Ignoring cache info: Caching catalog at /var/lib/puppet/state/localconfig.yaml notice: Starting catalog run err: //Node[engine2]/engine/packages/Set_file[/etc/munin/munin-node.conf]/File[/etc/munin/munin-node.conf]/ensure: change from absent to file failed: Could not set file on ensure: No such file or directory – /etc/munin/munin-node.conf.puppettmp at /etc/puppet/manifests/site.pp:7 notice: //Node[engine2]/engine/packages/Package[munin-node]: Dependency file[/etc/munin/munin-node.conf] has 1 failures warning: //Node[engine2]/engine/packages/Package[munin-node]: Skipping because of failed dependencies notice: Finished catalog run in 3.95 seconds
#5 Updated by Marc DiBlasi over 2 years ago
Wow, 3 years old and I just ran into this in 2.7.6. It popped up for me with some config files when I was changing my postgresql 8.4 manifest to have an option for 9.0. I had a config file at “/var/lib/pgsql/data/postgresql.conf” which now needs to be at “/var/lib/pgsql/9.0/data/postgresql.conf” and I got “change from absent to file failed: Could not set ‘file on ensure: No such file or directory – /var/lib/pgsql/data/postgresql.conf.puppettmp_6045”
Since the error looked like it was saying the puppettmp file didn’t exist, I thought it might be a puppet bug. I spent a couple hours trying to figure this out, someone should definitely look into this.