Issue #5934 has been updated by Matt Robinson.
I was going to update this ticket but saw Luke already did. Here's a little more context for how we ran into this same issue. ---------- Forwarded message ---------- From: Luke Kanies <[email protected]> Date: Tue, Apr 12, 2011 at 6:32 PM Subject: Re: (Zynga blocker) You cannot save facts to the code store; it is only used for getting facts from Facter To: Matt Robinson <[email protected]> Cc: [email protected], Jeff McCune <[email protected]> Good catch. This could easily be a load issue - that conditional is evaluated when defaults.rb is loaded, which might be happening after the application_name is being set. It seems like a difference between the 'puppetmasterd' app, which probably sets it quite early, and the unicorn support, which probably just sets it later in the process. This fix seems perfectly sufficient, though. On Apr 12, 2011, at 6:28 PM, Matt Robinson wrote: > I've been chatting with Jeff and we have something that fixes the > issue superficially. If he just passes `fact_terminus=yaml` on the > puppet master invocation it works under unicorn. Not sure why > fact_terminus is ever getting set to facter when running as the puppet > master, but Jeff is moving on for now and will do some more root cause > analysis later. > > I thought maybe the puppet application_name was getting set wrong in > defaults somehow, but that turned out not to be the case. > > :facts_terminus => { :default => Puppet.application_name.to_s > == "master" ? 'yaml' : 'facter', > > But when Jeff checked Puppet.application_name.to_s in his debug session: > > (rdb:1) e Puppet.application_name.to_s > "master" > (rdb:1) e Puppet[:facts_terminus] > "facter" > > As far as I can tell from acking around the facts_terminus only gets > set from lib/puppet/defaults.rb or lib/puppet/application/agent.rb, so > it's a mystery how it's not in line with what you expect defaults to > set. ---------------------------------------- Bug #5934: cannot save facts to the code store; it is only used for getting facts from Facter https://projects.puppetlabs.com/issues/5934 Author: Scott Nottingham Status: Closed Priority: Normal Assignee: Category: Target version: Affected Puppet version: Keywords: Branch: Affected Dashboard version: This error occurs when client tries to run: err: Could not retrieve catalog from remote server: Error 400 on SERVER: You cannot save facts to the code store; it is only used for getting facts from Facter It appears to be an issue on server side, but I haven't been able to get any useful information from log files. Logs only report the same simple error. the server setup is: puppet 2.6.4 + passenger 2.2.11 + rack 1.0.1 storeconfigs is enabled with mysql database -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://projects.puppetlabs.com/my/account -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/puppet-bugs?hl=en.
