Issue #3001 has been updated by Markus Roberts. Status changed from Ready for Testing to Ready for Checkin
---------------------------------------- Bug #3001: Can't manage broken links http://projects.reductivelabs.com/issues/3001 Author: Markus Roberts Status: Ready for Checkin Priority: Normal Assigned to: Category: fileserving Target version: 0.25.4 Affected version: 0.25.2 Keywords: Branch: http://github.com/MarkusQ/puppet/tree/ticket/0.25.x/3001 This fell off one of the grab-bag symlink tickets as a low priority side issue since it's easy to workaround, and may be rendered obsolete if we refacter the symlink handling system, but I'm giving it its own ticket so we don't loose track of it. Give a manifest containing: node default { file {"/tmp/link_to_nowhere": links => manage, source => "puppet://localhost/fs/link_to_nowhere", } } and a fileserver.conf [fs] path /tmp/test_data/ allow * and a link in /tmp/test_data/ that points to the nonexistent file "only_on_client_file" lrwxr-xr-x 1 markus staff 7 Dec 31 10:20 link_to_nowhere -> only_on_client_file where the intent is to produce a link to a target (only_on_client_file) on the client that corresponds to the target of the specified source (link_to_nowhere) but does not exist on the server, we get the following error on the client: err: //Node[default]/File[/tmp/link_to_nowhere]: Failed to retrieve current state of resource: Could not retrieve information from source(s) puppet://localhost/fs/link_to_nowhere at manifests/site.pp:17 and on the server: info: File does not exist or is not accessible: /tmp/test_data/link_to_nowhere info: Could not find file_metadata for 'fs/link_to_nowhere' Any attempt to fix this without a general refactoring should be weighed against the risk of reversion on the other symlink tickets fixed in 0.25.2. -- 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://reductivelabs.com/redmine/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.
