Re: [Puppet Users] Anyone made parser = future working on CentOS 6.5 Ruby 1.8.x?

2014-11-22 Thread Larry Liu
/lib/ruby/site_ruby/rgen/metamodel_builder/mm_multiple.rb:14:in 
`instance_eval'
/usr/lib/ruby/site_ruby/rgen/metamodel_builder/mm_multiple.rb:14:in 
`MMMultiple'
/usr/lib/ruby/site_ruby/rgen/metamodel_builder/mm_multiple.rb:12:in `each'
/usr/lib/ruby/site_ruby/rgen/metamodel_builder/mm_multiple.rb:12:in 
`MMMultiple'
/usr/lib/ruby/site_ruby/rgen/ecore/ecore.rb:20
/usr/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in 
`gem_original_require'
/usr/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in `require'
/usr/lib/ruby/gems/1.8/gems/activesupport-2.3.5/lib/active_support/dependencies.rb:158:in
 
`require'
/usr/lib/ruby/site_ruby/1.8/puppet/pops/containment.rb:3
/usr/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in 
`gem_original_require'
/usr/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in `require'
/usr/lib/ruby/gems/1.8/gems/activesupport-2.3.5/lib/active_support/dependencies.rb:158:in
 
`require'
/usr/lib/ruby/site_ruby/1.8/puppet/pops.rb:22
/usr/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in 
`gem_original_require'
/usr/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in `require'
/usr/lib/ruby/gems/1.8/gems/activesupport-2.3.5/lib/active_support/dependencies.rb:158:in
 
`require'
/usr/lib/ruby/site_ruby/1.8/puppet/parser/parser_factory.rb:55:in 
`assert_rgen_installed'
/usr/lib/ruby/site_ruby/1.8/puppet/parser/parser_factory.rb:32:in 
`evaluating_parser'
/usr/lib/ruby/site_ruby/1.8/puppet/parser/parser_factory.rb:13:in `parser'
/usr/lib/ruby/site_ruby/1.8/puppet/node/environment.rb:541:in 
`perform_initial_import'
/usr/lib/ruby/site_ruby/1.8/puppet/node/environment.rb:276:in 
`known_resource_types'
/usr/lib/ruby/site_ruby/1.8/puppet/resource/type_collection_helper.rb:5:in 
`known_resource_types'
/usr/lib/ruby/site_ruby/1.8/puppet/parser/compiler.rb:551:in `initvars'
/usr/lib/ruby/site_ruby/1.8/puppet/context.rb:64:in `override'
/usr/lib/ruby/site_ruby/1.8/puppet.rb:244:in `override'
/usr/lib/ruby/site_ruby/1.8/puppet/parser/compiler.rb:549:in `initvars'
/usr/lib/ruby/site_ruby/1.8/puppet/parser/compiler.rb:247:in `initialize'
/usr/lib/ruby/site_ruby/1.8/puppet/parser/compiler.rb:34:in `new'
/usr/lib/ruby/site_ruby/1.8/puppet/parser/compiler.rb:34:in `compile'
/usr/lib/ruby/site_ruby/1.8/puppet/indirector/catalog/compiler.rb:95:in 
`compile'
/usr/lib/ruby/site_ruby/1.8/puppet/util/profiler/around_profiler.rb:58:in 
`profile'
/usr/lib/ruby/site_ruby/1.8/puppet/util/profiler.rb:51:in `profile'
/usr/lib/ruby/site_ruby/1.8/puppet/indirector/catalog/compiler.rb:93:in 
`compile'
/usr/lib/ruby/site_ruby/1.8/puppet/util.rb:161:in `benchmark'
/usr/lib/ruby/1.8/benchmark.rb:308:in `realtime'
/usr/lib/ruby/site_ruby/1.8/puppet/util.rb:160:in `benchmark'
/usr/lib/ruby/site_ruby/1.8/puppet/indirector/catalog/compiler.rb:92:in 
`compile'
/usr/lib/ruby/site_ruby/1.8/puppet/indirector/catalog/compiler.rb:52:in 
`find'
/usr/lib/ruby/site_ruby/1.8/puppet/indirector/indirection.rb:201:in `find'
/usr/lib/ruby/site_ruby/1.8/puppet/application/master.rb:166:in `compile'
/usr/lib/ruby/site_ruby/1.8/puppet/application/master.rb:158:in 
`run_command'
/usr/lib/ruby/site_ruby/1.8/puppet/application.rb:384:in `run'
/usr/lib/ruby/site_ruby/1.8/puppet/application.rb:510:in `plugin_hook'
/usr/lib/ruby/site_ruby/1.8/puppet/application.rb:384:in `run'
/usr/lib/ruby/site_ruby/1.8/puppet/util.rb:488:in `exit_on_fail'
/usr/lib/ruby/site_ruby/1.8/puppet/application.rb:384:in `run'
/usr/lib/ruby/site_ruby/1.8/puppet/util/command_line.rb:146:in `run'
/usr/lib/ruby/site_ruby/1.8/puppet/util/command_line.rb:92:in `execute'
/usr/bin/puppet:8


On Saturday, November 22, 2014 1:11:56 PM UTC-8, Felix.Frank wrote:

 On 11/21/2014 04:16 PM, Larry Liu wrote: 
  Hi everyone, 
  
  According to puppetlab's doc, parser=future is supposed to work with 
  puppet version 3.5 or higher. I'm on 3.7.1 which falls under 
  
 https://docs.puppetlabs.com/puppet/latest/reference/experiments_future.html, 

  but it has not worked for me at all. Interestingly it works fine if I 
  run just CLI puppet apply --parser=future xyz.pp. Once I enable it on 
  my puppet masters, clients just keep getting 'Error: Could not 
  retrieve catalog from remote server: Error 400 on SERVER: Could not 
  parse for environment production: Do not add methods to model classes 
  directly, add them to the ClassModule instead on node xx'. The 
  ruby version on both masters and clients is 
 ruby-1.8.7.352-13.el6.x86_64. 
  
  Anyone know why? 

 The error is from rgen. 


 https://github.com/puppetlabs/puppet/blob/master/lib/puppet/vendor/rgen/lib/rgen/metamodel_builder.rb#L198
  

 It is unclear how your master triggers this. 

 Can you reproduce the error using `puppet master --compile node fqdn`? 
 If so, please add --trace and put the output somewhere for us to see. 

 Thanks, 
 Felix 


-- 
You received this message because you are subscribed to the Google Groups 
Puppet Users group.
To unsubscribe from this group and stop receiving emails

[Puppet Users] Anyone made parser = future working on CentOS 6.5 Ruby 1.8.x?

2014-11-21 Thread Larry Liu
Hi everyone,

According to puppetlab's doc, parser=future is supposed to work with puppet 
version 3.5 or higher. I'm on 3.7.1 which falls under 
https://docs.puppetlabs.com/puppet/latest/reference/experiments_future.html, 
but it has not worked for me at all. Interestingly it works fine if I run 
just CLI puppet apply --parser=future xyz.pp. Once I enable it on my puppet 
masters, clients just keep getting 'Error: Could not retrieve catalog from 
remote server: Error 400 on SERVER: Could not parse for environment 
production: Do not add methods to model classes directly, add them to the 
ClassModule instead on node xx'. The ruby version on both masters and 
clients is ruby-1.8.7.352-13.el6.x86_64.

Anyone know why?

-- 
You received this message because you are subscribed to the Google Groups 
Puppet Users group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/aa16b8e8-c503-42f2-9c41-26ea6e027023%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.