Jira (PDB-2628) PuppetDB Cached "trusted" fact causes puppet run's to fail with Error 400 on SERVER: Attempt to assign to a reserved variable name: 'trusted'
Title: Message Title Kenneth Barber commented on PDB-2628 Re: PuppetDB Cached "trusted" fact causes puppet run's to fail with Error 400 on SERVER: Attempt to assign to a reserved variable name: 'trusted' This problem as far as we're aware is only caused by a misconfigured routes.yaml, or misconfigured time between masters & agents which causes the master to ignore the cache and attempt to retrieve it from PuppetDB. Any case where it is trying to retrieve the facts from PDB is incorrect, which is why you are hitting this error as you have presumed. In a properly configured situation this should never happen. The key is to figure out why, and like I said its almost always one of those two reasons. Even if you remove the trusted key like you have, retrieving from PDB is still an error and will cause the master to always ignore your real facts. You state its puppet master --compile that generates the error, but what about puppet agent runs on the clients? Also, what version of Puppet is this? Double check that the routes.yaml is being read also, I often inject mistakes in routes.yaml to prove this, or strace it . The other thing to do is to ensure you have ntp running everywhere and that clock times between hosts are near identical, if there is any mistake there this will cause the master to use puppetdb because it believes the data it has received from the agent is old and fall back to PDB instead. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-2628) PuppetDB Cached "trusted" fact causes puppet run's to fail with Error 400 on SERVER: Attempt to assign to a reserved variable name: 'trusted'
Title: Message Title Robert Heinzmann commented on PDB-2628 Re: PuppetDB Cached "trusted" fact causes puppet run's to fail with Error 400 on SERVER: Attempt to assign to a reserved variable name: 'trusted' This file was automatically generated by the puppetdb module. — master: facts: terminus: puppetdb cache: yaml Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-2628) PuppetDB Cached "trusted" fact causes puppet run's to fail with Error 400 on SERVER: Attempt to assign to a reserved variable name: 'trusted'
Title: Message Title Wyatt Alt commented on PDB-2628 Re: PuppetDB Cached "trusted" fact causes puppet run's to fail with Error 400 on SERVER: Attempt to assign to a reserved variable name: 'trusted' Robert Heinzmann this is usually caused by a misconfigured or missing routes.yaml. Can you please give the output of this? cat $(puppet config print confdir)/routes.yaml Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-2628) PuppetDB Cached "trusted" fact causes puppet run's to fail with Error 400 on SERVER: Attempt to assign to a reserved variable name: 'trusted'
Title: Message Title
Robert Heinzmann created an issue
PuppetDB / PDB-2628
PuppetDB Cached "trusted" fact causes puppet run's to fail with Error 400 on SERVER: Attempt to assign to a reserved variable name: 'trusted'
Issue Type:
Bug
Affects Versions:
PDB 2.3.8
Assignee:
Unassigned
Components:
Platform
Created:
2016/04/18 1:27 AM
Environment:
[root@puppet]# rpm -qf /usr/share/ruby/vendor_ruby/puppet/indirector/facts/puppetdb.rb puppetdb-terminus-2.3.8-1.el7.noarch
[root@puppet]# rpm -qa | grep puppet puppet-3.8.6-1.el7.noarch puppetserver-1.1.3-1.el7.noarch puppetdb-2.3.8-1.el7.noarch puppetdb-terminus-2.3.8-1.el7.noarch
os => {"name"=>"CentOS", "family"=>"RedHat", "release"=> {"major"=>"7", "minor"=>"2", "full"=>"7.2.1511"}
}
Priority:
Normal
Reporter:
Robert Heinzmann
If trusted_node_data = true in [master], and agent provides /etc/puppet/csr_attributes.yaml puppet run's fail with
