On Fri, Jan 27, 2012 at 10:27 AM, rvlinden <[email protected]> wrote: > Hi all, > > I just upgraded a client with puppet 2.7.9 to 2.7.10 and now the > authorized_keys started to loop > > notice: /Stage[main]/Authorizedkey::UserX/ > Authorizedkey::Manage[userx_dss_domainx_test]/ > Ssh_authorized_key[userx_dss_domainx_test]/options: options changed > 'no-port-forwarding,no-agent-forwarding,no-X11-forwarding' to 'no-port- > forwarding,no-agent-forwarding,no-X11-forwarding' > > It says it changed .ssh/authorized_keys, but when I compare the > current authorized_keys in the user's homedir with the one in the > filebucket, they are identical. The only difference is the date/ > timestamp > > diff > < # HEADER: This file was autogenerated at Fri Jan 27 16:10:31 +0100 > 2012 > --- >> # HEADER: This file was autogenerated at Fri Jan 27 16:12:58 +0100 2012 > > It only loops on authorized keys with options, which are configured as > an array like this > > options => [ > 'no-port-forwarding', > 'no-agent-forwarding', > 'no-X11-forwarding', > ]
Perhaps a variation of this issue: http://projects.puppetlabs.com/issues/12197 There's an ongoing thread, and check if you have Ruby 1.8.7. Nan -- You received this message because you are subscribed to the Google Groups "Puppet Users" 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-users?hl=en.
