Issue #2124 has been updated by James Turnbull.

Status changed from Ready for Checkin to Closed

Pushed in commit:"172422fc0422e2646c4cc3afb7955876651cbf3e" in branch master.
----------------------------------------
Bug #2124: ssh_authorized_key always changes target if target is not defined
http://projects.reductivelabs.com/issues/2124

Author: Tony Jenness
Status: Closed
Priority: Normal
Assigned to: Francois Deppierraz
Category: ssh
Target version: 0.25.0
Complexity: Unknown
Affected version: 0.24.8
Keywords: 


This one looks to be a continuation of 
http://projects.reductivelabs.com/issues/2004 when you don't specify a target 
you get target changed output on every run. This was not the case in 0.24.7

*target not defined*
<pre>
ssh_authorized_key { "t...@test":
   ensure => present,
   key => 'AAAAAA',
   type => "ssh-rsa",
   user => "test",
}
</pre>
In 0.24.8 produces 
<pre>
notice: 
//Node[tjtest.obuops.bskyb.com]/base/users::obuops/ssh_authorized_key[t...@test]/target:
 target changed '/home/test/.ssh/authorized_keys' to 
'/home/test/.ssh/authorized_keys'
info: Filebucket[/var/lib/puppet/clientbucket]: Adding 
/home/test/.ssh/authorized_keys(765bc34f409feb56228f6fc93eaf108b)
</pre>

In 0.24.7 produces no output

*target defined*
<pre>
ssh_authorized_key { "t...@test":
   ensure => present,
   target => '/home/test/.ssh/authorised_keys',
   key => 'AAAAAA',
   type => 'ssh-rsa',
   user => 'test',
}
</pre>

In 0.24.7 & 0.24.8 produces no output


-- 
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to