Enter code here... Well, at least I've already checked all the things you're asking about. While the problem is frustrating, I do hate proving I'm a complete idiot to the internet :)
On Tuesday, December 5, 2017 at 1:50:10 PM UTC-6, Christopher Wood wrote: > > Quoth your earlier post: > > [[snip]] > > What does the ENC return for that node? The ENC is listed under the > "external_nodes" parameter in /etc/puppetlabs/puppet/puppet.conf, you > should be able to run it at the console like "/usr/bin/myenc nodename" sort > of thing. > cl1vinfconf2442 is my puppet server. The enc output looks like: # enc cl1vinfconf2442.mydom.com --- classes: - roles::mpipsrv environment: production parameters: env: prd dc: cl1 gw: 10.168.65.254 dmz: false auth: ldap grp: NULL > I notice you are missing a colon in your hiera key, should that be > "mpiossec::run_ossec"? The class::param delimiter is two colons. > Also quite correct. My earlier attempts at that did have the two colons. To verify that it still returns the same: # puppet lookup --environment production --node cl1vinfconf2442.mydom.com --explain mpiossec::run_ossec Error: Could not run: Could not find a directory environment named 'unconfigured' anywhere in the path: /etc/puppetlabs/code/environments. Does the directory exist? You are again correct that there is no /etc/puppetlabs/code/environments/unconfigured. Just to see what would happen, I did create a soft-link from unconfigured to production. I didn't get the error anymore... just didn't get anything at all. Now that I think of it, I ran those tests looking for fqdn.. let's try mpiossec::run_ossec: ... Hey, would you look at that # puppet lookup --node cl1vinfconf2442.mydom.com mpiossec::run_ossec --- true I'm beginning to suspect I know what's going on. The ENC will return an environment of 'unconfigured' for any node it doesn't know about. It's basically a catch-all that never gets used because in order to get that far a node has to have a cert which it won't get without being in the same database that the enc queries. so maybe ;puppet lookup' is getting the unconfigured from the enc and freaking before iet gets to the environment switch... I could probably confirm that by tracing the pid but, if an unconfigured env will get this working, I'm happy. ... Partially working as it turns out. it's still not accepting any puppet environment change. Any rate, this will get me started. thanks for the responses. Doug O'Leary -- 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/34250c91-b266-484d-b4c2-f4f561d835dd%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
