On Monday, January 12, 2015 at 4:49:50 PM UTC-6, puppetrier wrote:
>
> I am trying to assign classes to node either through site.pp or a custom
> ENC and I am getting nowhere.
> The nodes successfully receive empty catalogs from the master.
>
I suggest leaving ENCs out of the picture for the time being. For the
moment, focus on classifying nodes via your site manifest. Fewer moving
parts are involved.
> No signs of errors that I can see in any of the log files - the system
> just silently fails to apply my settings.
>
>
[...]
> Is there a way to turn up the verbose level and to follow how the master
> processes catalog requests from individual nodes?
>
>
You should be able to start the master with --debug logging enabled to get
more output on that side.
Since your nodes receive empty catalogs instead of no catalogs at all, you
are already over the first hump. The master acknowledges your nodes as
valid, known clients. If it is not assigning any classes or resources to
them then that's because it doesn't think any have been matched to those
node. The most likely possibilities are these:
- You are attempting to classify your nodes via a site manifest for a
different environment than the one tow which your nodes are assigned (or
via a manifest that is not actually a site manifest at all, name
notwithstanding).
- Your master is using a cached copy of the nodes' environment
- You disagree with Puppet with respect to which node identifier to use
to classify nodes. Puppet the master uses the name specified on the node's
SSL certificate (accessible also as $client_cert). The agent chooses the
node's fqdn as its certname by default, but that can be altered.
Things to try first off:
1. Create a "default" node block in your site manifest, and put a notify
resource in it: notify{"I am ${client_cert}": }. Delete or comment out
all other node blocks, so that the default block will be matched to every
node. This can be used to verify that you are working with the right site
manifest.
2. After changing your manifests, restart the puppetmaster service to
ensure that the environment cache is cleared.
If your nodes do not receive the Notify resource in their catalogs after
you do both of those, then you are working with the wrong site manifest.
If they do receive the resource, then the message it produces in the log
provides an identifier you can use as a node name to classify that node.
(For FQDNs, Puppet also allows the short form of that name as a node name.)
Beyond that, it's a question of declaring the classes you want assigned.
In particular, be aware that installing Puppet modules in the master does
not automatically cause them to be applied to your nodes (that would make
it impossible to give different nodes different configuration). Your node
blocks (and/or ENC) must specify to Puppet which classes should be applied
to each node -- that's the essence of "classification". In its simplest
form, you do that via 'include' statements in your node blocks.
Anyway, this is already starting to go speculative. Let us know what
happens when you try the above suggestions.
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/e25a905e-a442-4e94-b3fc-f95365c3d775%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
