Puppet users - Jun 2013 - Can't find source of "Removing mount" errors

I''m maintaining part of a rather large puppet config and at a loss to 
figure out where the following errors are coming from during a puppet 
update:

err: Removing mount all: /var/lib/puppet/files/all does not exist or is not 
a directory
err: Removing mount pixel: /var/lib/puppet/files/pixel does not exist or is 
not a directory
err: Removing mount compute: /var/lib/puppet/files/compute does not exist 
or is not a directory
err: Removing mount other: /var/lib/puppet/files/other does not exist or is 
not a directory
err: Removing mount storage: /var/lib/puppet/files/storage does not exist 
or is not a directory
err: Removing mount storage-solaris: /var/lib/puppet/files/storage-solaris 
does not exist or is not a directory

Searching for these strings in our config yields nothing and I''m really
not
sure where to go from here.  This puppet 2.6.4 on a CentOS 5.4 box.  Any 
ideas?

Thanks.

-- 
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 post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Hi,

You sure that a grep for ''mount'' through your manifest finds
nothing?

Looks a bit odd to me.

Den


On Thu, Jun 13, 2013 at 5:26 AM, Brandon <bwmetcalf@gmail.com> wrote:
> I''m maintaining part of a rather large puppet config and at a loss
to
> figure out where the following errors are coming from during a puppet
> update:
>
> err: Removing mount all: /var/lib/puppet/files/all does not exist or is
> not a directory
> err: Removing mount pixel: /var/lib/puppet/files/pixel does not exist or
> is not a directory
> err: Removing mount compute: /var/lib/puppet/files/compute does not exist
> or is not a directory
> err: Removing mount other: /var/lib/puppet/files/other does not exist or
> is not a directory
> err: Removing mount storage: /var/lib/puppet/files/storage does not exist
> or is not a directory
> err: Removing mount storage-solaris: /var/lib/puppet/files/storage-solaris
> does not exist or is not a directory
>
> Searching for these strings in our config yields nothing and I''m
really
> not sure where to go from here.  This puppet 2.6.4 on a CentOS 5.4 box.
>  Any ideas?
>
> Thanks.
>
> --
> 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 post to this group, send email to puppet-users@googlegroups.com.
> Visit this group at http://groups.google.com/group/puppet-users?hl=en.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>
>
-- 
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 post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

On Thursday, June 13, 2013 1:34:32 AM UTC-5, denmat
wrote:
>
> Hi, 
>
> You sure that a grep for ''mount'' through your manifest
finds nothing?
>
>
Yes, that''s what I was about to recommend.  And it is necessary to
check
all manifest locations -- the ''manifests'' subdirectory of
every directory
in the module path (recursively), the entry-point manifest (normally 
site.pp), and every manifest ''import''ed by any of those
manifests
(recursively).

It is not sufficient to search for the mount-point directory names, because 
these do not necessarily exist as complete strings anywhere in the 
manifests.  They may instead be assembled at need from two or more parts, 
one or both of which may be variables.  Some variables involved could even 
be provided by Puppet rather than declared in any manifest.

I can think of at least one way to obfuscate manifests so that the
''mount''
resource type name would not appear either, but I cannot imagine that 
happening accidentally, and I''m not up for helping overcome intentional
manifest obfuscation.


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 puppet-users+unsubscribe@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?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

I''ve searched, but haven''t found anything.  I will continue
looking.

On Thursday, June 13, 2013 6:25:35 AM UTC-7, jcbollinger
wrote:
>
>
>
> On Thursday, June 13, 2013 1:34:32 AM UTC-5, denmat wrote:
>>
>> Hi, 
>>
>> You sure that a grep for ''mount'' through your
manifest finds nothing?
>>
>>
> Yes, that''s what I was about to recommend.  And it is necessary to
check
> all manifest locations -- the ''manifests'' subdirectory of
every directory
> in the module path (recursively), the entry-point manifest (normally 
> site.pp), and every manifest ''import''ed by any of those
manifests
> (recursively).
>
> It is not sufficient to search for the mount-point directory names, 
> because these do not necessarily exist as complete strings anywhere in the 
> manifests.  They may instead be assembled at need from two or more parts, 
> one or both of which may be variables.  Some variables involved could even 
> be provided by Puppet rather than declared in any manifest.
>
> I can think of at least one way to obfuscate manifests so that the
''mount''
> resource type name would not appear either, but I cannot imagine that 
> happening accidentally, and I''m not up for helping overcome
intentional
> manifest obfuscation.
>
>
> 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 puppet-users+unsubscribe@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.

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 puppet-users+unsubscribe@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.