Issue #3646 has been updated by Luke Kanies. Assigned to changed from Luke Kanies to James Turnbull
The server currently assumes that there are facts stored in $vardir/yaml/$node.yaml - i.e., it assumes that you've compiled that host's catalog before. If you haven't, then just store the facts there, and it should work fine. It should be pretty easy to write a ruby script that accepts a given node's facts and stores them there. ---------------------------------------- Feature #3646: no easy way to pass facts to "puppetmasterd --compile" http://projects.puppetlabs.com/issues/3646 Author: Alan Barrett Status: Needs design decision Priority: Normal Assigned to: James Turnbull Category: plumbing Target version: Affected version: 0.25.4 Keywords: Branch: When running "puppetmasterd --compile ${client_fqdn}", it appears that the catalog is compiled as if no facts about the client are available. Even $hostname and $fqdn are undefined. This can very easily lead to failure to compile the catalog, because most people refer to fact variables in their catalogs. It would be nice if there was a way of passing a file full of facts on the command line, e.g. "puppetmasterd --compile ${client_fqdn} --factsfile ${file_full_of_facts}". It might make sense to default to reading facts from a cache where they might have been saved on a previous run, such as /var/puppet/yaml/facts/${client_fqdn}.yaml. -- 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.
