Regarding that fqdn and uptime_seconds are facts, that is understood. The agent node updating the file and triggered the content change may be obvious to you, but I'm a puppet beginner, and I yet don't have a solid understanding of the catalog run or how, when or where the tags get updated.
1. I thought that the file on the agent node would never be updated unless the content on the puppet master changed which would trigger the catalog run and force the update. 2. Instead, it appears that the agent node will trigger an update per it's runinterval, resolve the dynamic tags and if a fact needs updating, it will update the corresponding file and generate the content changed message I saw in the the agent node log. Is this close to correct? Meanwhile I'm going through ProPuppet and everything I can find on the puppetlabs site and hope to have a better understanding. On Thursday, August 22, 2013 10:00:38 AM UTC-6, Stephen Gran wrote: > > On 22/08/13 16:39, Ed Young wrote: > > Thanks for the response. There doesn't seem to be another process > > updating the files on before the puppet run. I believe the issue was the > > presence of a dynamic tag on the template file. > > > > The problem appears to be that the tag <%= @uptime_seconds %> was in > > some of the configuration files. When I removed that tag from the apache > > config files, and from the tomcat6 config files, there were no longer > > any updates due to file changes. > > > > The <%= @uptime_seconds %> appears to be set before execution of the > > puppet run, which I didn't expect, since tags such as <%= @fqdn %> > > resolve on the target agent node. > > > > Does this sound correct? > > if so, how do I know which tags or variables will be set before the > > puppet execution, and which are set on the agent side after the catalog > > run? > > @uptime_seconds and @fqdn are both facts. Facts are supplied by the > agent. In this case, uptime_seconds is how many seconds the node has > been up. This will obviously change between runs. For a list of what > facts are available, you can run `facter -p` on the node. > > Cheers, > -- > Stephen Gran > Senior Systems Integrator - theguardian.com > Please consider the environment before printing this email. > ------------------------------------------------------------------ > Visit theguardian.com > > On your mobile, download the Guardian iPhone app theguardian.com/iphoneand > our iPad edition > theguardian.com/iPad > Save up to 32% by subscribing to the Guardian and Observer - choose the > papers you want and get full digital access. > Visit subscribe.theguardian.com > > This e-mail and all attachments are confidential and may also > be privileged. If you are not the named recipient, please notify > the sender and delete the e-mail and all attachments immediately. > Do not disclose the contents to another person. You may not use > the information for any purpose, or store, or copy, it in any way. > > Guardian News & Media Limited is not liable for any computer > viruses or other material transmitted with or as part of this > e-mail. You should employ virus checking software. > > Guardian News & Media Limited > > A member of Guardian Media Group plc > Registered Office > PO Box 68164 > Kings Place > 90 York Way > London > N1P 2AP > > Registered in England Number 908396 > > -------------------------------------------------------------------------- > > -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users. For more options, visit https://groups.google.com/groups/opt_out.
