On Tuesday, May 1, 2012 12:00:19 PM UTC-4, Eric Lake wrote:
>
> I am wondering what would cause a puppet client to get into a state like
> this. I had a test vm do the same thing to me today.
>
>
>
Since nobody else responded first let me say thanks for posting the correct
syntax - I googled the
ut I know that if you run puppet with the
> --test option it forces puppet to ignore the cache which is a lot less
> annoying then editing the yaml file. I suppose in the puppet.conf for your
> clients you could put ignorecache = true and it will always compile the
> manifest for yo
In my testing, puppet has never caught on to a new config or recipe to
distribute unless I manually delete the node entry from the yaml/nodes
directory. I couldn't find any documentation on how to clear the
cache properly (I stumbled on that method) and I couldn't find any
documentation on how lo
