Puppet users - Oct 2014 - runinterval vs 'puppet agent --test'

I'm a new puppet user; just now doing some testing in a sandbox environment.

I have added 'runinterval' to the [agent] section of puppet.conf on one 
agent and set it to 60.   I can see (via 'tail -f /var/log/messages | grep 
puppet:') now that I get a "Notice:  Compiled catalog for myagent in 
environment production in 0.00 seconds' message every minute now on the 
puppet server so I'm assuming the new runinterval has taken effect on the 
one agent.

However, when I make a change for that node in a manifest on the server, it 
doesn't get pushed to the agent at its next check in.  In this case the 
change is to have telnet installed on the agent.  So, on the agent i'm 
testing with a 'which telnet' and it doesn't find /usr/bin/telnet.

So, being impatient, from the agent  I run 'puppet agent --test' and it 
then installs telnet.  So, I manually remove it (yum remove telnet) and 
wait to see when puppet will install it again.  I don't see it happening 
though unless i force it with the 'puppet agent --test' run on the
agent.

I'm sure I'm missing something in my understanding of what should be 
happening.  When the agent 'checks in' once every 60 seconds (because of
my
runinterval setting on the agent, shouldn't it detect that the actual 
configuration doesn't match the manifest and then install telnet again?

Thanks in advance for guidance!

Gene

-- 
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+unsubscribe@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/41bca65a-120d-4d5f-b47c-e583fcee8b4e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.