Issue #3922 has been updated by Simon Effenberg.
I have the same problem with 2.6.1 and the problem here is:
there is a /etc/skel/.ssh/authorized_keys so when i create a new user:
user { paul: } and he has a ssh_authroized_key { "p...@local": } then a
filebucket saves the authorized_keys, which was copied during useradd from
skel, as user paul..
now creating a second user:
user { pete: } with an ssh_authorized_key {} then a filebucket, using the same
md5 hash (its the same empty file) tries to save the old authorized_keys as
user pete but can't save it because there is an existing one owned by paul.. if
i change the content of /home/pete/.ssh/authorized_keys with something stupid
like "# xxxxxxxxxxxxxxxxx" then the next puppet run works and backup the file
as user pete..
so the main question for me is, is the design to backup files only on there md5
hash really a good idea? I don't know much about the usage of filebucket but
when more then one file can be saved within a md5 hash based directory (like
for the one with empty files) then only one user should be used to
create/update these files.. and if not more than one file can be saved within
one md5 hash then especially emtpy files will be a pain when creating all the
files as the origin owned user..
----------------------------------------
Bug #3922: Ssh_authorized_key "Could not apply complete catalog: Could not back
up"
https://projects.puppetlabs.com/issues/3922
Author: mélanie Gault
Status: Accepted
Priority: Normal
Assignee:
Category: ssh
Target version: queued
Affected Puppet version: 0.25.5
Keywords: backup clientbucket catalog Ssh_authorized_key
Branch:
I manage user, directories, ssh_authorized_key, ... on redhat 4 and 5 boxes
with a master and a client with 0.25.5 version.
My puppet client runs as root and my maser with the user puppet.
Everything works fine for some of my users, but I got an error with
clientbucket directory :
<pre>info: Caching catalog for puppet-client
info: Applying configuration version '1275367180'
notice: //users/My::User[my.user]/Ssh_authorized_key[my.user]/ensure: created
err: Could not apply complete catalog: Could not back up
/home/my.user/.ssh/authorized_keys: Permission denied -
/var/lib/puppet/clientbucket/f
notice: Finished catalog run in 3.52 seconds</pre>
If I create manualy this directory I got the same error for
/var/lib/puppet/clientbucket/f/6 next for /var/lib/puppet/clientbucket/f/6/9...
And at the end I have :
<pre>[r...@monserveur: i386 ]$ puppetd --server my-puppet -t -o
info: Caching catalog for puppet-client
info: Applying configuration version '1275367180'
notice: //users/My::User[my.user]/Ssh_authorized_key[my.user]/ensure: created
err: Could not apply complete catalog: Could not back up
/home/my.user/.ssh/authorized_keys: Permission denied -
/var/lib/puppet/clientbucket/f/6/9/4/9/5/1/7/f6949517cbf4fddfa665d41361f8bce4
notice: Finished catalog run in 3.69 seconds</pre>
manifest citation :
<pre> ssh_authorized_key { $name:
ensure => $ensure,
type => "dsa",
key => $key,
user => $name,
require => File["/home/$name/.ssh"],
}
</pre>
With 0.25.3 I didn't have this issue.
--
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.
