I''ve got a couple of custom facts that are used to find template paths etc. I always thought facts and plugins got pulled down before the modules were applied (this is 2.6.x), but it looks like they aren''t (having re-provisioned some nodes the initial run is failing immediately). I end up with invalid paths in the templates, so the run fails, so the facts never come down, rinse, repeat. Is there a way around this? -- 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+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
I''ve got a couple of custom facts that are used to find template paths etc. I always thought facts and plugins got pulled down before the modules were applied (this is 2.6.x), but it looks like they aren''t (having re-provisioned some nodes the initial run is failing immediately). I end up with invalid paths in the templates, so the run fails, so the facts never come down, rinse, repeat. Is there a way around this? -- 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+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Hi Dick, Do you have "pluginsync = true" in your Agent''s config in it''s initial run? Are the facts in a module''s path correctly (<module>/lib/facter/<fact>.rb) ? -Luke On 24/05/12 11:57, Dick Davies wrote:> I''ve got a couple of custom facts that are used to find template paths etc. > > I always thought facts and plugins got pulled down before the modules > were applied > (this is 2.6.x), but it looks like they aren''t (having re-provisioned > some nodes the initial > run is failing immediately). > > I end up with invalid paths in the templates, so the run fails, so the > facts never > come down, rinse, repeat. > > Is there a way around this? >-- Luke Bigum Information Systems Ph: +44 (0) 20 3192 2520 luke.bigum@lmax.com | http://www.lmax.com LMAX, Yellow Building, 1A Nicholas Road, London W11 4AN FX and CFDs are leveraged products that can result in losses exceeding your deposit. They are not suitable for everyone so please ensure you fully understand the risks involved. The information in this email is not directed at residents of the United States of America or any other jurisdiction where trading in CFDs and/or FX is restricted or prohibited by local laws or regulations. The information in this email and any attachment is confidential and is intended only for the named recipient(s). The email may not be disclosed or used by any person other than the addressee, nor may it be copied in any way. If you are not the intended recipient please notify the sender immediately and delete any copies of this message. Any unauthorised copying, disclosure or distribution of the material in this e-mail is strictly forbidden. LMAX operates a multilateral trading facility. Authorised and regulated by the Financial Services Authority (firm registration number 509778) and is registered in England and Wales (number 06505809). Our registered address is Yellow Building, 1A Nicholas Road, London, W11 4AN. -- 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+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Dick Davies
2012-May-24 15:27 UTC
Re: [Puppet Users] when are facts supposed to be synced?
They are, but have just realised they only get pushed out in the initial
puppet run...hum, bit of a catch 22 here.
Wondering if it''s inheritance related, normally we do something like
class thing_using_custom_facts {
include standardbuild_which_setsup_puppetconf
include module_needing_custom_facts
}
but these boxes are built with
class thing_using_custom_facts inherits standardbuild_which_setsup_puppetconf {
include module_needing_custom_facts
}
Maybe that''s the issue, anyone know? If not, will test tomorrow and
report back.
On 24 May 2012 13:14, Luke Bigum <Luke.Bigum@lmax.com>
wrote:> Hi Dick,
>
> Do you have "pluginsync = true" in your Agent''s config
in it''s initial run?
> Are the facts in a module''s path correctly
(<module>/lib/facter/<fact>.rb) ?
>
> -Luke
>
>
> On 24/05/12 11:57, Dick Davies wrote:
>>
>> I''ve got a couple of custom facts that are used to find
template paths
>> etc.
>>
>> I always thought facts and plugins got pulled down before the modules
>> were applied
>> (this is 2.6.x), but it looks like they aren''t (having
re-provisioned
>> some nodes the initial
>> run is failing immediately).
>>
>> I end up with invalid paths in the templates, so the run fails, so the
>> facts never
>> come down, rinse, repeat.
>>
>> Is there a way around this?
>>
>
>
> --
> Luke Bigum
>
> Information Systems
> Ph: +44 (0) 20 3192 2520
> luke.bigum@lmax.com | http://www.lmax.com
> LMAX, Yellow Building, 1A Nicholas Road, London W11 4AN
>
>
> FX and CFDs are leveraged products that can result in losses exceeding
> your deposit. They are not suitable for everyone so please ensure you
> fully understand the risks involved. The information in this email is not
> directed at residents of the United States of America or any other
> jurisdiction where trading in CFDs and/or FX is restricted or prohibited
> by local laws or regulations.
>
> The information in this email and any attachment is confidential and is
> intended only for the named recipient(s). The email may not be disclosed
> or used by any person other than the addressee, nor may it be copied in
> any way. If you are not the intended recipient please notify the sender
> immediately and delete any copies of this message. Any unauthorised
> copying, disclosure or distribution of the material in this e-mail is
> strictly forbidden.
>
> LMAX operates a multilateral trading facility. Authorised and regulated by
> the Financial Services Authority (firm registration number 509778) and
> is registered in England and Wales (number 06505809). Our registered
address
> is Yellow Building, 1A Nicholas Road, London, W11
> 4AN.
--
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+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
Ryan Coleman
2012-May-24 15:44 UTC
Re: [Puppet Users] when are facts supposed to be synced?
On Thu, May 24, 2012 at 8:27 AM, Dick Davies <rasputnik@hellooperator.net> wrote:> They are, but have just realised they only get pushed out in the initial > puppet run...hum, bit of a catch 22 here.New plugins do get transferred to an agent with pluginsync = true before the actual Puppet run. If your plugins change on the master, the next agent run would retrieve the modified/new content. This would occur before the agent run that retrieves your catalog with the classes that need your custom content. http://docs.puppetlabs.com/guides/plugins_in_modules.html If you didn''t catch the log and want to see if the plugins were transferred, try looking inside your agents libdir: `puppet agent --configprint libdir` -- 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+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.