Hi, you've probably seen this, but there are issues in 2.7.10 such as
http://projects.puppetlabs.com/issues/show/12310 http://projects.puppetlabs.com/issues/show/12269 http://projects.puppetlabs.com/issues/show/12269 http://projects.puppetlabs.com/issues/show/12588 I haven't checked whether either of them could be a culprit here. Your safest bet is possibly to downgrade from 2.7.10. Otherwise, you will have to "bisect" the manifest of an afflicted node, i.e. empty its node {} definition and re-include its classes in chunks of 50% iteratively. This may be more or less simple depending on your manifests. HTH, Felix On 02/16/2012 07:08 AM, Andreas Roth wrote: > Hi, > > i've upgraded many of my client machines to version 2.7.10 lately and > since on some clients (server is running 2.7.10) i get the following > error (running puppetd -tvd --noop --trace): > /usr/lib/ruby/1.8/puppet/simple_graph.rb:181:in `<=>' > /usr/lib/ruby/1.8/puppet/simple_graph.rb:181:in `sort' > /usr/lib/ruby/1.8/puppet/simple_graph.rb:181:in `find_cycles_in_graph' > /usr/lib/ruby/1.8/puppet/simple_graph.rb:221:in > `report_cycles_in_graph' > /usr/lib/ruby/1.8/puppet/transaction.rb:369:in `traverse' > /usr/lib/ruby/1.8/puppet/transaction.rb:99:in `evaluate' > /usr/lib/ruby/1.8/puppet/resource/catalog.rb:141:in `apply' > /usr/lib/ruby/1.8/puppet/configurer.rb:121:in > `retrieve_and_apply_catalog' > /usr/lib/ruby/1.8/puppet/util.rb:180:in `benchmark' > /usr/lib/ruby/1.8/benchmark.rb:308:in `realtime' > /usr/lib/ruby/1.8/puppet/util.rb:179:in `benchmark' > /usr/lib/ruby/1.8/puppet/configurer.rb:120:in > `retrieve_and_apply_catalog' > /usr/lib/ruby/1.8/puppet/configurer.rb:151:in `run' > /usr/lib/ruby/1.8/puppet/agent.rb:46 > /usr/lib/ruby/1.8/puppet/agent/locker.rb:11:in `lock' > /usr/lib/ruby/1.8/puppet/agent.rb:46 > /usr/lib/ruby/1.8/sync.rb:230:in `synchronize' > /usr/lib/ruby/1.8/puppet/agent.rb:46 > /usr/lib/ruby/1.8/puppet/agent.rb:110:in `with_client' > /usr/lib/ruby/1.8/puppet/agent.rb:44 > /usr/lib/ruby/1.8/puppet/application.rb:172:in `call' > /usr/lib/ruby/1.8/puppet/application.rb:172:in `controlled_run' > /usr/lib/ruby/1.8/puppet/agent.rb:42:in `run' > /usr/lib/ruby/1.8/puppet/application/agent.rb:344:in `onetime' > /usr/lib/ruby/1.8/puppet/application/agent.rb:318:in `run_command' > /usr/lib/ruby/1.8/puppet/application.rb:309:in `run' > /usr/lib/ruby/1.8/puppet/application.rb:413:in `hook' > /usr/lib/ruby/1.8/puppet/application.rb:309:in `run' > /usr/lib/ruby/1.8/puppet/application.rb:404:in `exit_on_fail' > /usr/lib/ruby/1.8/puppet/application.rb:309:in `run' > /usr/sbin/puppetd:4 > err: Got an uncaught exception of type NoMethodError: undefined method > `<=>' for #<Puppet::Type::Whit:0x2b04297cc470> > > Til now i don't have a clue which resources are causing the problem. > How shall i proceed? > > Thanks, > Andreas > -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
