Stages would not really help in this situation since manifests would be evaluated before plugins are synced in this scenario, the pluginsync would need to be set to true for it to be done before the manifest is compiled. One way I combated the problem is to use "production" environment as a node on-boarding set of manifests to get it up to date and prepped for its current environment and I have other environments defined for specific purposes. The other way would be to use if statements to check for the fact being there. If the value is nil, then its not there.
From: puppet-users@googlegroups.com [mailto:puppet-users@googlegroups.com] On Behalf Of Dan Carley Sent: Wednesday, August 03, 2011 5:29 AM To: puppet-users@googlegroups.com Subject: Re: [Puppet Users] pluginsync before catalogue? On 3 August 2011 04:38, josbal <joshua.bald...@gmail.com> wrote: Hi All, I have an issue with puppet where we are getting errors on some of our new built servers where the catalogue is trying to render before distributing custom facts that are required to render the catalogue correctly. We are running puppet 2.6.6 server and client. Error: err: Could not retrieve catalog from remote server: Error 400 on SERVER: Failed to parse template sudo/sudoers: Could not find value for 'customfact1' at /etc/puppet/default/modules/sudo/manifests/ init.pp:11 on node host.example.com Its my understanding the 'customfact1' fact is meant to be transferred to the host as part of the pluginsync process before the catalogue is rendered, but this doesn't seem to be happening on our new builds from the above error. Does anyone have any insight into the pluginsync/catalogue process and how this is fixable? The "pluginsync" config var defaults to false. I believe there's a ticket to default it to true in the future. But until that happens you have a few options: 1. Populate "pluginsync = true" in "puppet.conf" before the first run. 2. Use the "--pluginsync" argument on the first run 3. Possibly use stages to send out the correct "puppet.conf" before any modules use variables that are populated by custom facts. -- 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. -- 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.
