On Thursday, June 20, 2013 4:51:41 PM UTC-5, Brandon wrote:
>
> I've searched, but haven't found anything. I will continue looking.
>
>
Look out for declarations of this form:
resources { 'mount': purge => true }
Something like that ought to turn up in searches for "mount", but perhaps
you overlooked it because it is not a mount resource itself.
If you have storeconfigs enabled, then look out also for declarations of
this form:
Mount <<| [optional predicate] |>>
That might escape your notice if you are performing case-sensitive searches.
Really, though, this ought not to be so hard. Look at the master's
configuration file (puppet.conf) and the options with which the master
process is launched to determine the entry-point manifest (default:
/etc/puppet/manifests/site.pp) and the modulepath (default:
/etc/puppet/modules). Perform a recursive text search of the manifests in
those locations. Crudely, something like
grep -R '[Mm]ount' /etc/puppet/manifests /module/path/dir1 ...
/module/path/dirN
ought to locate the offending declaration(s), though you may need to filter
out or sift through false positives. Maybe many of them.
Also, check the logs on the agent to make sure that it is successfully
retrieving a fresh catalog, and restart the master to be certain that it
doesn't overlook any changed files.
John
--
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 [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.
