Issue #6819 has been updated by Cristian Tomoiaga.
Sorry for the late answer. I am not sure what exactly I did some time ago, most likely I cleared everything in authorized_keys and add all the keys in puppet. After that everything worked without a problem. Right now things are working fine. 1. The above manifest only has one key as an example. I had many other keys in the same class with only one class at that moment in the puppet server since I was testing. However, I was testing with only one key like in the example and with many keys, the result was the same at that time, the file was getting cleared every time I ran puppet. 2. The user is present, I only added keys in puppet that were already present in authorized_keys files. 3. I didn't do anything else, no files/directories shipped/created ---------------------------------------- Bug #6819: ssh_authorized_key empty authorized_keys for users other than root https://projects.puppetlabs.com/issues/6819 Author: Cristian Tomoiaga Status: Investigating Priority: Normal Assignee: Stefan Schulte Category: provider Target version: Affected Puppet version: Keywords: ssh_authorized_key Branch: Hello everyone, I just installed puppet: Client 2.6.6 on CentOS 5.5 from epel-testing Server 2.6.2-4~bpo50+1 on Ubuntu 10.04.1 from Debian repo (same issue with the default package, tried and sticked with the Debian for now) Using the manifest below (tried with different variants, added name, changed from rsa to dss a.s.o.) will result in an empty authorized_keys file for user. I also tried adding target but the result is the same, the file is still empty. The file will be emptied/recreated each time puppet runs. class ssh_keys { ssh_authorized_key { "rsa-key-20110323": user => "test", key => "AAAAB...=", type => "ssh-rsa", ensure => "present", } } If I change from user test to root everything works ok. puppet agent --test info: Caching catalog for [server hostname] info: Applying configuration version '1300902056' notice: /Stage[main]/Ssh_keys/Ssh_authorized_key[rsa-key-20110323]/ensure: created info: FileBucket got a duplicate file {md5}d41d8cd98f00b204e9800998ecf8427e notice: Finished catalog run in 0.36 seconds "FileBucket got a duplicate file" won't appear on the first run, after that it will be there everytime. -- 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.
