Issue #4285 has been updated by James Turnbull. Status changed from Unreviewed to Accepted Target version set to 2.6.0
I can replicate this: <pre> /usr/lib/ruby/site_ruby/1.8/puppet/indirector/rest.rb:57:in `deserialize' /usr/lib/ruby/site_ruby/1.8/puppet/indirector/rest.rb:71:in `find' /usr/lib/ruby/site_ruby/1.8/puppet/indirector/indirection.rb:193:in `find' /usr/lib/ruby/site_ruby/1.8/puppet/indirector.rb:50:in `find' /usr/lib/ruby/site_ruby/1.8/puppet/configurer.rb:225:in `retrieve_new_catalog' /usr/lib/ruby/site_ruby/1.8/puppet/util.rb:414:in `thinmark' /usr/lib/ruby/1.8/benchmark.rb:308:in `realtime' /usr/lib/ruby/site_ruby/1.8/puppet/util.rb:413:in `thinmark' /usr/lib/ruby/site_ruby/1.8/puppet/configurer.rb:224:in `retrieve_new_catalog' /usr/lib/ruby/site_ruby/1.8/puppet/configurer.rb:102:in `retrieve_catalog' /usr/lib/ruby/site_ruby/1.8/puppet/configurer.rb:143:in `run' /usr/lib/ruby/site_ruby/1.8/puppet/agent.rb:39:in `run' /usr/lib/ruby/site_ruby/1.8/puppet/agent/locker.rb:21:in `lock' /usr/lib/ruby/site_ruby/1.8/puppet/agent.rb:39:in `run' /usr/lib/ruby/1.8/sync.rb:230:in `synchronize' /usr/lib/ruby/site_ruby/1.8/puppet/agent.rb:39:in `run' /usr/lib/ruby/site_ruby/1.8/puppet/agent.rb:101:in `with_client' /usr/lib/ruby/site_ruby/1.8/puppet/agent.rb:37:in `run' /usr/lib/ruby/site_ruby/1.8/puppet/application.rb:171:in `call' /usr/lib/ruby/site_ruby/1.8/puppet/application.rb:171:in `controlled_run' /usr/lib/ruby/site_ruby/1.8/puppet/agent.rb:35:in `run' /usr/lib/ruby/site_ruby/1.8/puppet/agent.rb:76:in `start' /usr/lib/ruby/site_ruby/1.8/puppet/external/event-loop/signal-system.rb:95:in `call' /usr/lib/ruby/site_ruby/1.8/puppet/external/event-loop/signal-system.rb:95:in `__signal__' /usr/lib/ruby/site_ruby/1.8/puppet/external/event-loop/signal-system.rb:95:in `each' /usr/lib/ruby/site_ruby/1.8/puppet/external/event-loop/signal-system.rb:95:in `__signal__' (eval):2:in `signal' /usr/lib/ruby/site_ruby/1.8/puppet/external/event-loop/event-loop.rb:313:in `sound_alarm' /usr/lib/ruby/site_ruby/1.8/puppet/agent.rb:80:in `start' /usr/lib/ruby/site_ruby/1.8/puppet/daemon.rb:124:in `start' /usr/lib/ruby/site_ruby/1.8/puppet/application/agent.rb:132:in `main' /usr/lib/ruby/site_ruby/1.8/puppet/application/agent.rb:89:in `run_command' /usr/lib/ruby/site_ruby/1.8/puppet/application.rb:301:in `run' /usr/lib/ruby/site_ruby/1.8/puppet/application.rb:398:in `exit_on_fail' /usr/lib/ruby/site_ruby/1.8/puppet/application.rb:301:in `run' /usr/lib/ruby/site_ruby/1.8/puppet/util/command_line.rb:55:in `execute' /usr/bin/puppet:4 err: Could not retrieve catalog from remote server: Error 400 on SERVER: Puppet::Parser::AST::Resource failed with error ArgumentError: Cannot alias File[file2] to [nil]; resource ["File", [nil]] already exists at /etc/puppet/modules/sudo/manifests/init.pp:11 on node pelin.lovedthanlost.net info: Not using expired catalog for pelin.lovedthanlost.net from cache; expired at Sun Jul 18 17:32:13 -0700 2010 notice: Using cached catalog err: Could not retrieve catalog; skipping run debug: Using cached certificate for ca debug: Using cached certificate for pelin.lovedthanlost.net debug: Using cached certificate_revocation_list for ca debug: Value of 'preferred_serialization_format' (pson) is invalid for report, using default (yaml) debug: report supports formats: b64_zlib_yaml marshal raw yaml; using yaml </pre> ---------------------------------------- Bug #4285: ArgumentError: Cannot alias File[mytitle] to [nil] http://projects.puppetlabs.com/issues/4285 Author: Alan Barrett Status: Accepted Priority: Normal Assigned to: Category: Target version: 2.6.0 Affected version: 2.6.0rc4 Keywords: Branch: With puppet 2.6.0rc4, I get the following error: <pre> Puppet::Parser::AST::Resource failed with error ArgumentError: Cannot alias File[mytitle] to [nil]; resource ["File", [nil]] already exists at /dir/filename.pp:25 on node myhost.domain.example </pre> The offending part of the manifest is <pre> file { "mytitle": name => "/dir/subdir/file", source => "puppet:///modules/mymodule/file", } </pre> Most of my file resources do not have explicit "name" parameters", and have the full path name in the title parameter. The error appears to be triggered by the second file resource that has an explicit "name" parameter. I have been unable to create a small standalone manifest that demonstrates the problem. -- 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.
