Jira (PUP-1428) No such file or directory error with ssh_authorized_keys

[Daniel Dreier (JIRA)]

Title: Message Title

Daniel Dreier commented on an issue   Re: No such file or directory error with ssh_authorized_keys This was originally reported against 2.7.14. About two years ago, the original reporter figured out what the matter was: "I was mounting my tmp folder to another volume and that folder was not writable. I did not know that puppet writes to /tmp. Should we display a warning if tmp cannot be written to? The error message, in its current form, is not easy to debug." As of puppet 3.6.2, error messages for a read-only /tmp are more descriptive. For the following test manifest, and given a loopback filesystem mounted read-only to /tmp, we get the output below: ssh_authorized_key { 'daniel': key => 'testkey', type => ssh-rsa, user => 'daniel', require => User['daniel'], } user { 'daniel': ensure => 'present', managehome => true, } [root@poss-head-centos ~]# puppet apply test.pp Warning: Future reserved word: type. Either choose a different name or quote the string, if possible. In /root/test.pp:3. See http://links.puppetlabs.com/reserved-words-4 (at /puppetlabs/puppet/lib/puppet/parser/lexer.rb:615:in `warn_if_reserved') Notice: Compiled catalog for poss-head-centos.puppetdebug.vlan in environment production in 0.34 seconds Error: Could not set 'present' on ensure: Read-only file system - /tmp/puppet20140619-9394-rzb8kx.lock at 11:/root/test.pp Error: Could not set 'present' on ensure: Read-only file system - /tmp/puppet20140619-9394-rzb8kx.lock at 11:/root/test.pp Wrapped exception: Read-only file system - /tmp/puppet20140619-9394-rzb8kx.lock Error: /Stage[main]/Main/User[daniel]/ensure: change from absent to present failed: Could not set 'present' on ensure: Read-only file system - /tmp/puppet20140619-9394-rzb8kx.lock at 11:/root/test.pp Notice: /Stage[main]/Main/Ssh_authorized_key[daniel]: Dependency User[daniel] has failures: true Warning: /Stage[main]/Main/Ssh_authorized_key[daniel]: Skipping because of failed dependencies Notice: Finished catalog run in 0.09 seconds Given the fact that the original issue was essentially misconfiguration exacerbated by a confusing error message, and the error message is much more descriptive now, I think this issue can safely be closed. Add Comment   Puppet / PUP-1428 No such file or directory error with ssh_authorized_keys When I try to set authorized keys through the ssh_authorized_key resource type, I get the following error:     Could not evaluate: Puppet::Util::FileType::FileTypeFlat could not write /home/nitesh/.ssh/authorized_keys: No such file or directory - /opt/puppet/lib/puppet20120417-2519-62ftr9.lock      $vardir config is set to /opt/puppet/lib. I am savin... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.