Issue #5257 has been updated by Andrew Parker. Target version deleted (2.7.x)
---------------------------------------- Bug #5257: Files written to non-existent directories get confusing error messages https://projects.puppetlabs.com/issues/5257#change-80300 Author: Jordan Sissel Status: Accepted Priority: Normal Assignee: Category: Target version: Affected Puppet version: Keywords: usability Branch: This is a common report in #puppet on freenode: <pre> 14:45 < astrostl> getting a "change from absent to file failed" on that one, with a "no such file or directory bar.puppettmp_2893" </pre> The cause is an attempt to write a file to a directory that does not exist, for example: <pre> ops(~) !127! % puppet apply -e 'file { "/tmp/path/does/not/exist/myfile": ensure => file, content => "Hello"; }' err: /Stage[main]//File[/tmp/path/does/not/exist/myfile]/ensure: change from absent to file failed: Could not set 'file on ensure: No such file or directory - /tmp/path/does/not/exist/myfile.puppettmp_7620 at line 1 <pre> This error message gets confusing right about the time it says ".puppettmp_..." - It would be much better if this error message said more explicitly something like: "Could not set file on ensure: Directory does not exist: /tmp/path/does/not/exist" - or something similar. -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://projects.puppetlabs.com/my/account -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/puppet-bugs?hl=en.
