Here's my test (done on Debian Stable with puppet 2.7.13 from the puppetlabs
apt repository):
$ cat /tmp/t1.pp
file { '/tmp/xx/yy/zz/1':
ensure => absent,
}
$ ls /tmp/xx
ls: cannot access /tmp/xx: No such file or directory
$ puppet apply /tmp/t1.pp
notice: Finished catalog run in 0.02 seconds
$ touch /tmp/xx
$ puppet apply /tmp/t1.pp
err: /Stage[main]//File[/tmp/xx/yy/zz/1]: Could not evaluate: Not a directory -
/tmp/xx/yy/zz/1
notice: Finished catalog run in 0.02 seconds
It seems counter-intuitive that if /tmp/xx is a regular file then this causes
the manifest run to fail. If /tmp/xx is a regular file then /tmp/xx/yy/zz/1
can't exist. Does anybody use this behaviour for anything?
I found this while testing if it would work with only one subdirectory of a
deep path, without realizing that /tmp/xx was a regular file not a directory.
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
