Jira (PDB-949) Retrieving facts that have had 'trusted' facts injected into them causes a 400 "Attempt to assign to a reserved variable name: 'trusted' on node" failure during Puppet catalog compilation.

[Joshua Partlow (JIRA)]

Title: Message Title

Joshua Partlow commented on an issue   Re: Retrieving facts that have had 'trusted' facts injected into them causes a 400 "Attempt to assign to a reserved variable name: 'trusted' on node" failure during Puppet catalog compilation. We have useful logs of the failure from a PE 3.4 run finally. It looks to be SERVER-38 preventing a read of the YAML cache, falling back to puppetdb and then you get a node with 'trusted' in it's parameters and the scope throws an error. More details in PUP-3277 if anyone is curious. Add Comment   PuppetDB / PDB-949 Retrieving facts that have had 'trusted' facts injected into them causes a 400 "Attempt to assign to a reserved variable name: 'trusted' on node" failure during Puppet catalog compilation. We are seeing some failures in the PE Puppet Acceptance Tests job where the nodes facts contain a 'trusted' parameter which is reserved and ends up failing when the compiler pulls the facts into scope. {noformat} s60whm7u1kz3zfm.delivery.puppetlabs.net (redhat6-64-1) 09:08:56$ env PATH="/opt/puppet/bin:${PATH}" RUBYLIB="${RUBYLIB}" puppet agent --te... 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 https://groups.google.com/d/optout.