Issue #3745 has been updated by Markus Roberts. Status changed from Unreviewed to Ready for Testing Branch set to git://github.com/seanmil/puppet.git ticket/0.25.x/3745
+1 on the list to both the problem and the fix, with the possible (and minor) question of the wording of the message. ---------------------------------------- Bug #3745: ssh_authorized_key provider can raise an unhandled exception http://projects.puppetlabs.com/issues/3745 Author: Sean Millichamp Status: Ready for Testing Priority: Normal Assigned to: Category: ssh Target version: Affected version: 0.25.4 Keywords: ssh_authorized_key ArgumentError Branch: git://github.com/seanmil/puppet.git ticket/0.25.x/3745 If you use ssh_authorized_key and specify the user but not the target AND the user does not exist at the time Puppet processes ssh_authorized_key, a unhandled ArgumentError error is raised from File.expand_path. This will abort Puppet's execution run and prevent remaining resources from being applied. I encountered this problem in our imaging process, where a system is imaged and receives an initial Puppet run on a network where it is unable to contact an LDAP server that will eventually provide the required user. Until then, Puppet should not be prevented from finishing other resources. I have a patch and a test for this issue which I will make available via git as soon as I know what ticket number this is so I can name the branch properly... -- 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.
