Issue #1915 has been updated by Daniel Pittman. Target version changed from 2.7.x to 2.7.9
---------------------------------------- Bug #1915: File resources fail when original is a dangling symlink https://projects.puppetlabs.com/issues/1915#change-57168 Author: micah - Status: Closed Priority: Normal Assignee: Category: file Target version: 2.7.9 Affected Puppet version: 0.24.7 Keywords: Problem #85 Branch: If before puppet has run, my host has the following dangling symlink: <pre> $ ls -l /etc/motd lrwxrwxrwx 1 root root 13 2006-09-26 23:46 /etc/motd -> /var/run/motd $ ls -ld /var/run/motd ls: cannot access /var/run/motd: No such file or directory </pre> Then I define a file resource for this host as follows: <pre> file{"/etc/motd": content => ("foo"), owner => root, group => 0, mode => 0644; } </pre> Puppet then files to create that file, due to the dangling symlink: <pre> err: //motd::client/File[/etc/motd]: Failed to retrieve current state of resource: Could not read /etc/motd: No such file or directory - /etc/motd </pre> I've tried various parameters to the file resource to override this such as backup => false, link => ignore, force => true and they all fail. It seems like puppet should just remove the dangling symlink and replace it with what should be there, rather than error when the current state of the resource is in error. -- 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.
