On Tue, May 22, 2012 at 2:59 PM, Erik Dalén <erik.gustav.da...@gmail.com> wrote: > After some tweaks I got a 3.0 puppetmaster and client working. But if > I try a 3.0 client against a 2.7 master I get the following error: > Error: Failed to apply catalog: Could not intern from pson: source > '"#<Puppet::Node:0x7f' not in PSON!
That output is the default Ruby "stringification" of a class that doesn't otherwise support being turned into PSON. > I know it isn't generally supported to run new clients against older > master versions. But it would be very practical if it worked, is there > anything I could do to get that working? Any clues why this error > occurs? The 3.0.0 agent performs a node lookup to determine which environment the ENC (if any) expects it to be in. The 2.7 master doesn't support PSON encoding for the node object that is transferred as part of that - but apparently doesn't correctly error, just returns the default Ruby stringification of the object. You could use the routes.yaml file on the agent to change the node terminus from REST to something else (eg: plain or so) in order to avoid that check. That would bypass the specific issue, although we make absolutely no assurance that anything else will work correctly either. -- Daniel Pittman ⎋ Puppet Labs Developer – http://puppetlabs.com ♲ Made with 100 percent post-consumer electrons -- 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.
