Issue #2004 has been updated by bart.
We've been testing 0.24.8rc1 (upgrading from 0.24.5), and the only regression we've run into so far is this issue. I'm not sure how feasible it is, but should this be targeted for 0.24.8? ---------------------------------------- Bug #2004: ssh_authorized_key fails if no target is defined http://projects.reductivelabs.com/issues/2004 Author: immerda Status: Accepted Priority: Normal Assigned to: ctrlaltdel Category: Target version: Complexity: Unknown Affected version: 0.24.7 Keywords: ssh_authorized_key, target Latest version from 0.24.x fails with the following error if no target is defined: <pre> #puppet --trace --debug foo.pp debug: Creating default schedules debug: Prefetching parsed resources for ssh_authorized_key debug: //ssh_authorized_key...@foobar_root]: Changing ensure debug: //ssh_authorized_key...@foobar_root]: 1 change(s) notice: //ssh_authorized_key...@foobar_root]/ensure: created debug: Flushing ssh_authorized_key provider target /usr/lib/ruby/1.8/fileutils.rb:1262:in `initialize' /usr/lib/ruby/1.8/fileutils.rb:1262:in `open' /usr/lib/ruby/1.8/fileutils.rb:1262:in `copy_file' /usr/lib/ruby/1.8/fileutils.rb:1261:in `open' /usr/lib/ruby/1.8/fileutils.rb:1261:in `copy_file' /usr/lib/ruby/1.8/fileutils.rb:463:in `copy_file' /usr/lib/ruby/1.8/fileutils.rb:383:in `cp' /usr/lib/ruby/1.8/fileutils.rb:1395:in `fu_each_src_dest' /usr/lib/ruby/1.8/fileutils.rb:1411:in `fu_each_src_dest0' /usr/lib/ruby/1.8/fileutils.rb:1393:in `fu_each_src_dest' /usr/lib/ruby/1.8/fileutils.rb:382:in `cp' /usr/lib/ruby/site_ruby/1.8/puppet/util/filetype.rb:114:in `write' /usr/lib/ruby/site_ruby/1.8/puppet/util/filetype.rb:55:in `real_write' /usr/lib/ruby/site_ruby/1.8/puppet/util/filetype.rb:55:in `write' /usr/lib/ruby/site_ruby/1.8/puppet/provider/parsedfile.rb:102:in `flush_target' /usr/lib/ruby/site_ruby/1.8/puppet/provider/parsedfile.rb:74:in `flush' /usr/lib/ruby/site_ruby/1.8/puppet/provider/parsedfile.rb:72:in `each' /usr/lib/ruby/site_ruby/1.8/puppet/provider/parsedfile.rb:72:in `flush' /usr/lib/ruby/site_ruby/1.8/puppet/provider/parsedfile.rb:356:in `flush' /usr/lib/ruby/site_ruby/1.8/puppet/provider/ssh_authorized_key/parsed.rb:66:in `flush' /usr/lib/ruby/site_ruby/1.8/puppet/type.rb:855:in `flush' /usr/lib/ruby/site_ruby/1.8/puppet/transaction.rb:92:in `apply' /usr/lib/ruby/site_ruby/1.8/puppet/transaction.rb:239:in `eval_resource' /usr/lib/ruby/site_ruby/1.8/puppet/util.rb:425:in `thinmark' /usr/lib/ruby/gems/1.8/gems/activesupport-2.2.2/lib/active_support/core_ext/benchmark.rb:8:in `realtime' /usr/lib/ruby/site_ruby/1.8/puppet/util.rb:424:in `thinmark' /usr/lib/ruby/site_ruby/1.8/puppet/transaction.rb:238:in `eval_resource' /usr/lib/ruby/site_ruby/1.8/puppet/transaction.rb:310:in `evaluate' /usr/lib/ruby/site_ruby/1.8/puppet/util.rb:425:in `thinmark' /usr/lib/ruby/gems/1.8/gems/activesupport-2.2.2/lib/active_support/core_ext/benchmark.rb:8:in `realtime' /usr/lib/ruby/site_ruby/1.8/puppet/util.rb:424:in `thinmark' /usr/lib/ruby/site_ruby/1.8/puppet/transaction.rb:309:in `evaluate' /usr/lib/ruby/site_ruby/1.8/puppet/transaction.rb:303:in `collect' /usr/lib/ruby/site_ruby/1.8/puppet/transaction.rb:303:in `evaluate' /usr/lib/ruby/site_ruby/1.8/puppet/node/catalog.rb:124:in `apply' /usr/bin/puppet:233 err: Could not apply complete catalog: Puppet::Util::FileType::FileTypeFlat could not write : No such file or directory </pre> Content of foo.pp <pre> ssh_authorized_key{'x...@foobar_root': type => 'ssh-rsa', user => 'root', key => 'AAAAXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX=' } </pre> if I additionally define a target it works like a charm. ---------------------------------------- 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://reductivelabs.com/redmine/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 -~----------~----~----~----~------~----~------~--~---
