On Wednesday, January 14, 2015 at 7:10:01 AM UTC-6, puppetrier wrote:
>
> Some success: although I haven't solved the problem with site.pp (probably
> due to hiera configuring environment folders - that I still can't
> troubleshoot...) things start working with a custom ENC.
> One of the reaso
Some success: although I haven't solved the problem with site.pp (probably
due to hiera configuring environment folders - that I still can't
troubleshoot...) things start working with a custom ENC.
One of the reasons why ENC didn't work the first time was a class in
default master modules that
Thank you. The --debug option looks very useful.
Indeed there seems to be a problem with the environment config folder
location.
I assume the path in the "Did not match path" line bellow is not actually
referring to an absolute path...
Anyway, the class mapping still doesn't work. I made the
Man, so many typos today :(.
But also this error:
>
>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 nod
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
