When for some reason the catalog compilation fails and the cached
version is used on one node, all the exported resources from this node
appear to be deleted from the master and the node realizing those
resources acts as they don't exist, deleting them...
For instance, we have a node "A" exporting a specific file. A node "B"
is realizing this file into a directory with "purge=>true". When
compiling the catalog for node "A", there is a syntax error, the cached
version is used. If you try to compile the catalog in "B" before fixing
the syntax error in "A", the exported file will be deleted.
I know we could just set "purge=>false" so it doesn't delete it, but I
would like to maintain it.
Is that the proper behaviour for the exported resources? Is there any
way to avoid this issue?
Thanks
--
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.
