Issue #2351 has been updated by Peter Meier. Keywords changed from Francois, I upgraded production at work to .25.3 yesterday and have not seen this problem yet. The problem was at home however on a new machine. I have yet to provision a new box with the .25.3 master, so I am not sure if that may be a factor. to ssh
Copy for Joe McDonagh from Keywords: Francois, I upgraded production at work to .25.3 yesterday and have not seen this problem yet. The problem was at home however on a new machine. I have yet to provision a new box with the .25.3 master, so I am not sure if that may be a factor. ---------------------------------------- Bug #2351: ssh_authorized_key looks for authorized_keys even though target is authorized_keys2 http://projects.reductivelabs.com/issues/2351 Author: Joe McDonagh Status: Needs design decision Priority: Normal Assigned to: Francois Deppierraz Category: ssh Target version: 0.25.5 Affected version: 0.25.0beta1 Keywords: ssh Branch: Hi guys, getting this error on the .25 beta: notice: //Node[apt.phishnet.internal]/aptproxy_tmpl/basenode_tmpl/accounts/accounts::users/Accounts::Admin[jmcdonagh]/ssh_authorized_key[[email protected]]/target: target changed '/home/jmcdonagh/.ssh/authorized_keys' to '/home/jmcdonagh/.ssh/authorized_keys2' info: Filebucket[/var/lib/puppet/clientbucket]: Adding /home/jmcdonagh/.ssh/authorized_keys2(c96469ad574dd50286fcfdf42b4d8da8) err: Got an uncaught exception of type Errno::ENOENT: No such file or directory - /home/jmcdonagh/.ssh/authorized_keys -- 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.
