Bug #1532

ssh_authorized_keys fails when ~/.ssh does not exists

Added by Paul Boven over 3 years ago. Updated about 2 years ago.

Status:Rejected Start date:08/25/2008
Priority:Normal Due date:
Assignee:Francois Deppierraz % Done:

0%
Category:newfeature
Target version:-
Affected Puppet version:0.24.4 Branch:
Keywords:
Votes: 0

Description

notice: //Ssh_authorized_key[user@hostname]/ensure: created err: Could not apply complete catalog: Puppet::Util::FileType::FileTypeFlat could not write /home/user/.ssh/authorized_keys: No such file or directory – /home/user/.ssh/authorized_keys

Perhaps this provider should create the directory with appropriate permissions and ownership if it does not yet exist? Of course, a require => File[“/home/user/.ssh”] in the manifest with a suitable file entry solves this as well.

History

#1
Updated by James Turnbull over 3 years ago

  • Category set to newfeature
  • Status changed from Unreviewed to Accepted
  • Assignee set to Francois Deppierraz

#2
Updated by Francois Deppierraz over 3 years ago

  • Status changed from Accepted to Rejected

Same cause as issue #1549.

Also available in: Atom PDF