Bug #2736
Ssh_authorized_key target changed?
| Status: | Closed | Start date: | 10/19/2009 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: | - | % Done: | 0% |
|
| Category: | ssh | |||
| Target version: | 0.25.1 | |||
| Affected Puppet version: | 0.25.1rc2 | Branch: | > OTOH, I kind of like preemptively assigning tickets to releases, since it's otherwise hard to track what > tickets are in process and, if they reach a certain point, would get assigned. | |
| Keywords: | ssh_authorized_keys | |||
| Votes: | 1 |
Description
We have the following section in our manifest:
ssh_authorized_key { "authkeypuppet":
user => "puppet",
key => "AAAAA",
type => ssh-rsa,
name => "web@noc",
ensure => present,
require => User["puppet"],
require => File["/var/lib/puppet/.ssh"],
target => "/var/lib/puppet/.ssh/authorized_keys2"
}
With 0.24.8, all of this worked just fine. I upgraded puppetmaster to 0.25.1rc2, and everything was still fine ( with 0.24.8 clients ).
As soon as I upgraded a client to 0.25.1rc2, i started getting these errors:
root@web344:~# puppetd --test info: Caching catalog for web344 info: Applying configuration version '1255956842' notice: //puppet::common/Ssh_authorized_key[authkeypuppet]/target: target changed '/var/lib/puppet/.ssh/authorized_keys' to '/var/lib/puppet/.ssh/authorized_keys2' info: Filebucket[/var/puppet/clientbucket]: Adding /var/lib/puppet/.ssh/authorized_keys2(54ef083d83589a3c5c3436c13dbfbbb3) err: Got an uncaught exception of type Errno::ENOENT: No such file or directory - /var/lib/puppet/.ssh/authorized_keys notice: Finished catalog run in 0.81 seconds
/var/lib/puppet/.ssh/authorized_keys doesn’t exist ( it never did ), we’ve always used /var/lib/puppet/.ssh/authorized_keys2 ..
Related issues
History
Updated by Bart Verwilst over 2 years ago
Removing target => “/var/lib/puppet/.ssh/authorized_keys2” gets rid of the errors, but installs the file into /var/lib/puppet/.ssh/authorized_keys.
Updated by Luke Kanies over 2 years ago
- Category set to ssh
- Status changed from Unreviewed to Needs More Information
- Keywords set to ssh_authorized_keys
Anyone else having this problem?
This would certainly be a client-side issue, not server-side, so it’s got to be some difference between the two releases.
Updated by Markus Roberts over 2 years ago
My guess is that this is either related to or possibly a duplicate of #2685.
Updated by Markus Roberts over 2 years ago
I can now reproduce this.
Updated by Markus Roberts over 2 years ago
I’ve got a fix in the works. There are actually a number of interrelated issues here; target, basically, doesn’t work with user and doesn’t work quite right even without it.
Updated by Markus Roberts over 2 years ago
- Status changed from Needs More Information to In Topic Branch Pending Review
- Target version set to 0.25.1
- Branch set to > OTOH, I kind of like preemptively assigning tickets to releases, since it's otherwise hard to track what > tickets are in process and, if they reach a certain point, would get assigned.
Branch with fix up at http://github.com/MarkusQ/puppet/tree/ticket/master/2736.
Updated by Bart Verwilst over 2 years ago
Just tried your changes, confirmed to work like a charm! Thanks a lot for the great and speedy work!
Updated by James Turnbull over 2 years ago
- Status changed from In Topic Branch Pending Review to Closed
Pushed in commit:b4bcfe9106c43855fbb4d1d147945ddb0e08ab34 in branch 0.25.x