Jira (PUP-1235) enabling future parser breaks puppet - Do not add methods to model classes directly...
Title: Message Title Jason Antman commented on an issue Re: enabling future parser breaks puppet - Do not add methods to model classes directly... Comment from Chad Huneycutt (original Redmine requester) 3 months ago: I should have picked up on the activesupport/storedconfigs connection from the trace, but I am a little dense sometimes. When I disable storedconfigs, the problem goes away. I shouldnt be using activerecord storedconfigs anymore anyway, right? I am willing to help debug this more if you want to track it down, or I will just update my setup to use puppetdb. For the record, here are some other relevant versions: ruby-1.8.7.352-10.el6_4.x86_64 ruby-rgen-0.6.5-1.el6.noarch LOCAL GEMS activerecord (2.3.16) activesupport (2.3.16) daemon_controller (1.1.5) json (1.5.5) passenger (4.0.19) rack (1.5.2) rake (10.1.0) I'm going to close this as wont fix - activerecord-based storedconfigs are deprecated. Switching to PuppetDB should fix this (not to mention provide amazing performance benefits over the old storedconfigs system). Add Comment Puppet / PUP-1235 enabling future parser breaks puppet - Do not add methods to model classes directly... After enabling the future parser, agent runs fail with Could not parse for environment X: Do not add methods to model classes directly, add them to the ClassModule instead on node foo.bar This happens even with an empty node definition. up-to-date RHEL6.4 on master and agent with puppet 3.3.1 from puppetlabs repo The master is run via apache+pa...
Jira (PUP-1235) enabling future parser breaks puppet - Do not add methods to model classes directly...
Title: Message Title redmine.exporter created an issue Puppet / PUP-1235 enabling future parser breaks puppet - Do not add methods to model classes directly... Issue Type: Bug Assignee: Unassigned Created: 24/Dec/13 8:03 AM Labels: redmine Priority: Normal Reporter: redmine.exporter After enabling the future parser, agent runs fail with Could not parse for environment X: Do not add methods to model classes directly, add them to the ClassModule instead on node foo.bar This happens even with an empty node definition. up-to-date RHEL6.4 on master and agent with puppet 3.3.1 from puppetlabs repo The master is run via apache+passenger. puppet.conf on master: pre [main] dbadapter = mysql dbuser = puppet dbpassword = myultrasecretpassword dbserver = localhost dbsocket = /var/lib/mysql/mysql.sock [master] vardir = /var/lib/puppetmaster ssldir = /var/lib/puppetmaster/ssl rundir = /var/run/puppet autosign = true modulepath = /etc/puppet/environments/$environment/modules:/etc/puppet/environments/common/modules manifest = /etc/puppet/environments/$environment/site.pp hiera_config = /etc/puppet/hiera.yaml reports = log, foreman set default env for unconfigured nodes environment = infrastructure storeconfigs = true parser = future /pre
Jira (PUP-1235) enabling future parser breaks puppet - Do not add methods to model classes directly...
Title: Message Title Fabrice Bacchella commented on an issue Re: enabling future parser breaks puppet - Do not add methods to model classes directly... Got hit by this. What do you need to solve this ? Add Comment Puppet / PUP-1235 enabling future parser breaks puppet - Do not add methods to model classes directly... After enabling the future parser, agent runs fail with Could not parse for environment X: Do not add methods to model classes directly, add them to the ClassModule instead on node foo.bar This happens even with an empty node definition. up-to-date RHEL6.4 on master and agent with puppet 3.3.1 from puppetlabs repo The master is run via apache+pa... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit
