Issue #13973 has been updated by Nitesh Goel.
Hi there
The /opt/puppet/lib directory certainly exists because that is where my
manifests reside.
Here is my complete puppet apply statement:
/usr/local/bin/puppet apply --modulepath=/opt/puppet/lib/modules
--vardir=/opt/puppet/lib --debug /opt/puppet/lib/manifests/site.pp
This is what I see before the error
debug: Prefetching parsed resources for ssh_authorized_key
notice:
/Stage[appetizer]/Accounts::User::Nitesh/Accounts::Device::Shuriken[nitesh]/Ssh_authorized_key[nitesh@shuriken]/ensure:
created
debug: Creating /home/nitesh/.ssh
debug: Flushing ssh_authorized_key provider target
/home/nitesh/.ssh/authorized_keys
/usr/local/lib/ruby/1.9.1/tempfile.rb:346:in `rmdir'
/usr/local/lib/ruby/1.9.1/tempfile.rb:346:in `rmdir'
/usr/local/lib/ruby/1.9.1/tempfile.rb:338:in `ensure in locking'
/usr/local/lib/ruby/1.9.1/tempfile.rb:338:in `locking'
/usr/local/lib/ruby/1.9.1/tempfile.rb:144:in `block in initialize'
/usr/local/lib/ruby/1.9.1/tmpdir.rb:133:in `create'
/usr/local/lib/ruby/1.9.1/tempfile.rb:134:in `initialize'
/usr/local/lib/ruby/gems/1.9.1/gems/puppet-2.7.13/lib/puppet/util/filetype.rb:107:in
`new'
/usr/local/lib/ruby/gems/1.9.1/gems/puppet-2.7.13/lib/puppet/util/filetype.rb:107:in
`write'
/usr/local/lib/ruby/gems/1.9.1/gems/puppet-2.7.13/lib/puppet/util/filetype.rb:56:in
`block (2 levels) in newfiletype'
/usr/local/lib/ruby/gems/1.9.1/gems/puppet-2.7.13/lib/puppet/provider/parsedfile.rb:95:in
`flush_target'
/usr/local/lib/ruby/gems/1.9.1/gems/puppet-2.7.13/lib/puppet/provider/parsedfile.rb:69:in
`block in flush'
/usr/local/lib/ruby/gems/1.9.1/gems/puppet-2.7.13/lib/puppet/provider/parsedfile.rb:67:in
`each'
/usr/local/lib/ruby/gems/1.9.1/gems/puppet-2.7.13/lib/puppet/provider/parsedfile.rb:67:in
`flush'
/usr/local/lib/ruby/gems/1.9.1/gems/puppet-2.7.13/lib/puppet/provider/parsedfile.rb:341:in
`flush'
/usr/local/lib/ruby/gems/1.9.1/gems/puppet-2.7.13/lib/puppet/provider/ssh_authorized_key/parsed.rb:65:in
`block in flush'
/usr/local/lib/ruby/gems/1.9.1/gems/puppet-2.7.13/lib/puppet/util/suidmanager.rb:79:in
`asuser'
/usr/local/lib/ruby/gems/1.9.1/gems/puppet-2.7.13/lib/puppet/provider/ssh_authorized_key/parsed.rb:59:in
`flush'
/usr/local/lib/ruby/gems/1.9.1/gems/puppet-2.7.13/lib/puppet/type.rb:654:in
`flush'
/usr/local/lib/ruby/gems/1.9.1/gems/puppet-2.7.13/lib/puppet/transaction/resource_harness.rb:139:in
`evaluate'
/usr/local/lib/ruby/gems/1.9.1/gems/puppet-2.7.13/lib/puppet/transaction.rb:49:in
`apply'
/usr/local/lib/ruby/gems/1.9.1/gems/puppet-2.7.13/lib/puppet/transaction.rb:84:in
`eval_resource'
/usr/local/lib/ruby/gems/1.9.1/gems/puppet-2.7.13/lib/puppet/transaction.rb:104:in
`block (2 levels) in evaluate'
/usr/local/lib/ruby/gems/1.9.1/gems/puppet-2.7.13/lib/puppet/util.rb:467:in
`block in thinmark'
/usr/local/lib/ruby/1.9.1/benchmark.rb:295:in `realtime'
/usr/local/lib/ruby/gems/1.9.1/gems/puppet-2.7.13/lib/puppet/util.rb:466:in
`thinmark'
/usr/local/lib/ruby/gems/1.9.1/gems/puppet-2.7.13/lib/puppet/transaction.rb:104:in
`block in evaluate'
/usr/local/lib/ruby/gems/1.9.1/gems/puppet-2.7.13/lib/puppet/transaction.rb:386:in
`traverse'
/usr/local/lib/ruby/gems/1.9.1/gems/puppet-2.7.13/lib/puppet/transaction.rb:99:in
`evaluate'
/usr/local/lib/ruby/gems/1.9.1/gems/puppet-2.7.13/lib/puppet/resource/catalog.rb:141:in
`apply'
/usr/local/lib/ruby/gems/1.9.1/gems/puppet-2.7.13/lib/puppet/configurer.rb:122:in
`block in retrieve_and_apply_catalog'
/usr/local/lib/ruby/gems/1.9.1/gems/puppet-2.7.13/lib/puppet/util.rb:159:in
`block in benchmark'
/usr/local/lib/ruby/1.9.1/benchmark.rb:295:in `realtime'
/usr/local/lib/ruby/gems/1.9.1/gems/puppet-2.7.13/lib/puppet/util.rb:158:in
`benchmark'
/usr/local/lib/ruby/gems/1.9.1/gems/puppet-2.7.13/lib/puppet/configurer.rb:121:in
`retrieve_and_apply_catalog'
/usr/local/lib/ruby/gems/1.9.1/gems/puppet-2.7.13/lib/puppet/configurer.rb:152:in
`run'
/usr/local/lib/ruby/gems/1.9.1/gems/puppet-2.7.13/lib/puppet/application/apply.rb:229:in
`main'
/usr/local/lib/ruby/gems/1.9.1/gems/puppet-2.7.13/lib/puppet/application/apply.rb:149:in
`run_command'
/usr/local/lib/ruby/gems/1.9.1/gems/puppet-2.7.13/lib/puppet/application.rb:309:in
`block (2 levels) in run'
/usr/local/lib/ruby/gems/1.9.1/gems/puppet-2.7.13/lib/puppet/application.rb:416:in
`hook'
/usr/local/lib/ruby/gems/1.9.1/gems/puppet-2.7.13/lib/puppet/application.rb:309:in
`block in run'
/usr/local/lib/ruby/gems/1.9.1/gems/puppet-2.7.13/lib/puppet/application.rb:407:in
`exit_on_fail'
/usr/local/lib/ruby/gems/1.9.1/gems/puppet-2.7.13/lib/puppet/application.rb:309:in
`run'
/usr/local/lib/ruby/gems/1.9.1/gems/puppet-2.7.13/lib/puppet/util/command_line.rb:69:in
`execute'
/usr/local/lib/ruby/gems/1.9.1/gems/puppet-2.7.13/bin/puppet:4:in `<top
(required)>'
/usr/local/bin/puppet:23:in `load'
/usr/local/bin/puppet:23:in `<main>'
err:
/Stage[appetizer]/Accounts::User::Nitesh/Accounts::Device::Shuriken[nitesh]/Ssh_authorized_key[nitesh@shuriken]:
Could not evaluate: Puppet::Util::FileType::FileTypeFlat could not write
/home/nitesh/.ssh/authorized_keys: No such file or directory -
/opt/puppet/lib/puppet20120417-7787-ra5vpb.lock
----------------------------------------
Bug #13973: No such file or directory error with ssh_authorized_keys
https://projects.puppetlabs.com/issues/13973#change-60817
Author: Nitesh Goel
Status: Needs More Information
Priority: Normal
Assignee: Nitesh Goel
Category: ssh
Target version: 2.7.14
Affected Puppet version: 2.7.13
Keywords:
Branch:
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 saving my puppet manifests in a
git repo and running them locally without a puppet server.
--
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://projects.puppetlabs.com/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.
