Bug #2351
ssh_authorized_key looks for authorized_keys even though target is authorized_keys2
| Status: | Duplicate | Start: | 06/19/2009 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assigned to: |  Francois Deppierraz |
% Done: | 0% |
|
| Category: | ssh | |||
| Target version: | 0.25.5 | |||
| Affected version: | 0.25.0beta1 | Branch: | ||
| Keywords: | ssh | |||
| Votes: | 0 |
Description
Hi guys, getting this error on the .25 beta:
notice: //Node[apt.phishnet.internal]/aptproxy_tmpl/basenode_tmpl/accounts/accounts::users/Accounts::Admin[jmcdonagh]/Ssh_authorized_key[Joseph.E.McDonagh@gmail.com]/target: target changed ‘/home/jmcdonagh/.ssh/authorized_keys’ to ‘/home/jmcdonagh/.ssh/authorized_keys2’ info: Filebucket[/var/lib/puppet/clientbucket]: Adding /home/jmcdonagh/.ssh/authorized_keys2(c96469ad574dd50286fcfdf42b4d8da8) err: Got an uncaught exception of type Errno::ENOENT: No such file or directory – /home/jmcdonagh/.ssh/authorized_keys
History
Updated by James Turnbull about 1 year ago
- Category set to ssh
- Status changed from Unreviewed to Needs design decision
- Assigned to set to Francois Deppierraz
Updated by Markus Roberts 7 months ago
- Target version set to 0.25.3
Updated by Markus Roberts 7 months ago
- Target version changed from 0.25.3 to 0.25.4
Updated by James Turnbull 7 months ago
- Target version changed from 0.25.4 to 0.25.5
Updated by Francois Deppierraz 6 months ago
Joe McDonagh wrote:
notice: //Node[apt.phishnet.internal]/aptproxy_tmpl/basenode_tmpl/accounts/accounts::users/Accounts::Admin[jmcdonagh]/Ssh_authorized_key[Joseph.E.McDonagh@gmail.com]/target: target changed ‘/home/jmcdonagh/.ssh/authorized_keys’ to ‘/home/jmcdonagh/.ssh/authorized_keys2’ info: Filebucket[/var/lib/puppet/clientbucket]: Adding /home/jmcdonagh/.ssh/authorized_keys2(c96469ad574dd50286fcfdf42b4d8da8) err: Got an uncaught exception of type Errno::ENOENT: No such file or directory – /home/jmcdonagh/.ssh/authorized_keys
Sorry for the reply delay, can you please post a sample recipe which shows this bug? Thanks!
Updated by Joe McDonagh 6 months ago
- Keywords set to Francois, I upgraded production at work to .25.3 yesterday and have not seen this problem yet. The problem was at home however on a new machine. I have yet to provision a new box with the .25.3 master, so I am not sure if that may be a factor.
Updated by Peter Meier 6 months ago
- Keywords changed from Francois, I upgraded production at work to .25.3 yesterday and have not seen this problem yet. The problem was at home however on a new machine. I have yet to provision a new box with the .25.3 master, so I am not sure if that may be a factor. to ssh
Copy for Joe McDonagh from Keywords:
Francois, I upgraded production at work to .25.3 yesterday and have not seen this problem yet. The problem was at home however on a new machine. I have yet to provision a new box with the .25.3 master, so I am not sure if that may be a factor.
Updated by Francois Deppierraz 4 months ago
- Status changed from Needs design decision to Duplicate
It’s probably another occurrence of #2736 which was fixed in 0.25.1.