Jira (PUP-1050) ssh_authorized_key always changes from root to user on every run

[JIRA]

Title: Message Title

Jürgen Weber commented on an issue   Re: ssh_authorized_key always changes from root to user on every run I have this issue also. Versions: facter 1.7.3-1puppetlabs1 Ruby module for collecting simple facts about a host operating system hiera 1.2.1-1puppetlabs1 A simple pluggable Hierarchical Database. puppet 3.3.2-1puppetlabs1 Centralized configuration management - agent startup and compatibility scripts puppet-common 3.3.2-1puppetlabs1 Centralized configuration management puppetlabs-release 1.0-7 "Package to install Puppet Labs gpg key and apt repo" ruby-rgen 0.6.5-1puppetlabs1 A framework supporting Model Driven Software Development (MDSD) vim-puppet 3.3.2-1puppetlabs1 syntax highlighting for puppet manifests in vim and here are the logs: Mon Dec 16 12:56:32 +0000 2013 /Stage[main]/Profile_user/Profile_user::Usr[jweber]/Component_user::User[jweber]/Ssh_authorized_key[jweber]/key (notice): key changed '<insert pub key>' Mon Dec 16 12:56:32 +0000 2013 /Stage[main]/Profile_user/Profile_user::Usr[jweber]/Component_user::User[jweber]/Ssh_authorized_key[jweber]/user (notice): user changed 'root' to 'jweber' Mon Dec 16 12:56:32 +0000 2013 /Stage[main]/Profile_user/Profile_user::Usr[jweber]/Component_user::User[jweber]/Ssh_authorized_key[jweber]/target (notice): target changed '/root/.ssh/authorized_keys' to '/home/jweber/.ssh/authorized_keys' Mon Dec 16 12:56:32 +0000 2013 /Stage[main]/Profile_user/Profile_user::Usr[jweber]/Component_user::User[jweber]/Ssh_authorized_key[jweber]/options (notice): undefined 'options' from 'no-port-forwarding,no-agent-forwarding,no-X11-forwarding,command="echo 'Please login as the user \",ubuntu' Mon Dec 16 12:56:33 +0000 2013 Puppet (err): Puppet::Util::FileType::FileTypeFlat could not write /root/.ssh/authorized_keys: Permission denied - /root/.ssh/authorized_keys Mon Dec 16 12:56:33 +0000 2013 /Stage[main]/Profile_user/Profile_user::Usr[jweber]/Component_user::User[jweber]/Ssh_authorized_key[jweber] (err): Could not evaluate: Puppet::Util::FileType::FileTypeFlat could not write /root/.ssh/authorized_keys: Permission denied - /root/.ssh/authorized_keys Mon Dec 16 12:57:29 +0000 2013 Puppet (notice): Finished catalog run in 154.52 seconds To understand our environment we all login as users with keys and then we sudo to root if necessary. To run puppet one users 'sudo su -' and then runs puppet. I explain this because I feel the issue is environment related. It looks like to me that it is attempting to update the current users home env settings (root) as the user that was logged in via ssh (jweber). So as you can see it fails with permission errors but I do not understand the why it is even trying to do this? Sometimes it does not happen when you run puppet manually on the command line (but other times you do) and I can not work out why it does or does not happen. You can see this in the agent logs consistently but then again, sometimes it doesn't so it consistently as well. I am not sure if it is a puppet bug or something else but I started some searching and found this ticket. If you would like more information feel free to ask. Thanks Add Comment   Puppet / PUP-1050 ssh_authorized_key always changes from root to user on every run I have this in my manifest:     ssh_authorized_key {     "test" :     user => "root2",     ensure => present,     type => "ssh-rsa",     key => "AAAA <snip> ==";     } Whenever I run puppet it shows these notices:     notice: /Stage[main]/Ssh/Ssh_authorized_key[test]/user: user changed 'root' to 'root2' Is there anyway to suppress t... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.