Is there a way to blow away the cache and refresh? We don't use ENC in
this environment, just a simple site.pp, which references nodes.pp.
Segue, what I like about ENC is that you can call your homegrown script,
get a yaml of params, classes for that node. I wish I could get something
similar with site.pp. It would just be another level of debugging that
could prove helpful.
This is what I have in a nutshell (simplified version):
nodes.pp
============
node /^stg-resque[0-9][0-9].mycompany.com$/ inherits base {
$packages = [ 'ImageMagick', 'git', 'libxml2-devel', 'libxslt-devel', ...
]
include network, nrpe, deployenv, deployenv::rvm, ...
}
The problem, is that there are deployenv, deployenv::passenger, and
deployenv::rvm. Somehow, deployenv::passenger is being picked up, even
though it is not explicitly specified in the nodes.pp.
deployent/manifests/rvm.pp
================
class deployenv::rvm () {
exec { gems: ... }
exec { bundler: ... }
}
deployent/manifests/init.pp
================
class deployenv {
group { deploy: ...}
user { deploy: ...}
file { .ssh: ...}
file { deploy_dirs: ... }
}
deployent/manifests/passenger.pp
================
class deployenv::passenger () {
file { nginx.conf: ... }
exec { nginx_install: ...}
}
On Wednesday, February 12, 2014 6:27:15 AM UTC-8, jcbollinger wrote:
>
>
>
> On Tuesday, February 11, 2014 6:05:54 PM UTC-6, Joaquin Menchaca wrote:
>>
>> I was wondering is there is a way to see what puppet things a node
>> resource is, such as classes it includes. Somehow in our environment it is
>> picking up a class that we did not specify.
>>
>
>
> I could believe that you are getting a class that you did not realize you
> were declaring, or that you did not declare directly in manifest code
> written by you. I could believe that the agent is applying a cached
> catalog that contains a class that once was declared for the target node,
> but no longer is. I do not believe that the catalog compiler is randomly
> throwing in classes that were not in some way declared for the target node.
>
> With that said, it's not altogether clear to me what you're actually
> asking. I suspect that what you really want is to determine is where the
> unexpected class is declared, and for that purpose the 'grep' command is
> your friend. Search for the class's unqualified, lowercase name in your
> manifests and hiera data. If you use an ENC then you can run that manually
> and grep for the class name in its output.
>
>
> 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 view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/e4e9efe1-1ac9-432f-a7aa-5a8204ede731%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
