Issue #4057 has been updated by Alan Barrett.
The word "immediately" in the problem description makes me think that this is a filetimeout issue; hence not a bug. However, filetimeout could be documented much more prominently, given how many times people are surprised by it. ---------------------------------------- Bug #4057: update variable not always reflected immediatly in template http://projects.puppetlabs.com/issues/4057 Author: Johan Huysmans Status: Investigating Priority: Normal Assigned to: James Turnbull Category: functions Target version: 0.25.6 Affected version: 0.25.5 Keywords: Branch: In our setup we have a .pp file containing several variables. These variables are used in the templates. We've seen that when the variable is updated this is not immediately visible when running puppet on the clients. This means that puppet is run on the client after updating the variable and the old value still appears in the configuration file. This is how our pp files are structured site.pp <pre> import "variables.pp" node 'node_name' { include class2 } class class2 inherits class1 { ... } class class1 { file { "platform.config": name => "/etc/platform.config", content => template("ALL/etc/platform.config"), owner => "root", group => "root", mode => "0644", } } </pre> variables.pp <pre> $platformname = "some name" </pre> -- 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.
