2009/2/18 Luke Kanies <[email protected]> > > On Feb 18, 2009, at 5:56 AM, Matt wrote: > > > Hi, > > > > I've got a problem with puppet holding the nodes manifest in > > memory. I'm running Puppet 0.24.6. > > > > I'm using Ec2 nodes which means the DNS names are reused quite > > frequently. > > > > When starting new Ec2 instances I update the node manifest for that > > DNS, touch the site.pp manifest to update the master, wait 30 > > seconds then clean the certificate for that DNS/Ec2 node. > > > > Problem I have is that the Ec2 node on most occasions will pick up > > the old manifest file.. then eventually will pick up the one which > > is on disk. > > > > Has this been fixed recently? or is there another way I can work > > around it? > > > You should be able to set the filetimeout to something like 0 to force > it to look at the disk more often, but even then, it shouldn't take > more than 15 seconds (by default). > > If you absolutely don't want any stale data, another approach is an > external node tool. > > -- > Censorship, like charity, should begin at home; but, unlike charity, it > should end there. --Clare Booth Luce > --------------------------------------------------------------------- > Luke Kanies | http://reductivelabs.com | http://madstop.com > > > > > Cheers Luke, i'll give that a bash.
--~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Puppet Users" 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-users?hl=en -~----------~----~----~----~------~----~------~--~---
