similar to: Trouble with ENC and static.pp : enabling ENC fails to find node even with default node in site.pp

Hello, I''m trying to use External Node classification and I have not idea what is my mistake. I getting the following error : err: Could not retrieve catalog from remote server: Error 400 on SERVER: undefined method `downcase'' for ["hola", {"mens"=>"HOLA"}]:Array on node casa I have a very simple parameter class : class hola( $mens =

Hello, Is it possible to configure an ENC to provide class definition to a number of nodes at the same time where a few other nodes are controlled in the site.pp by node ''FQDN'' {blah} for the same puppetmaster ? I am wondering once parameters are set for the master to look for an ENC based definitions, will it conflict with the site.pp node definitions ? For example these

I''m trying to setup dashboard as a node classifier w/puppet 2.6.14. Not sure why this is not working... In puppet.conf on the master I have: node_terminus = exec external_nodes = /usr/bin/env PUPPET_DASHBOARD_URL=http:// localhost /usr/share/puppet-dashboard/bin/external_node The agent''s return: err: Could not retrieve catalog from remote server: Error 400 on SERVER:

puppet maser conf: [main] logdir = /var/log/puppet rundir = /var/run/puppet ssldir = $vardir/ssl [master] classfile = $vardir/classes.txt localconfig = $vardir/localconfig user = root group = root fileserverconfig = /etc/puppet/fileserver.conf reportdir = /home/logs/puppet/reports masterhttplog = /home/logs/puppet/masterhttp.log masterlog =

Hello All, So I finally got around to start to cut over node definitions from standard flat files to external nodes (foreman), and getting error message: "Error 400 on SERVER: Could not find node ''nodename''; cannot compile" - So basically it can''t pick up the node from the external node config. When I test the fetching of the yaml file it seems to work

Hi, I have a Puppet Enterprise (2.0) puppetmaster running with Foreman, and having trouble getting it working as an External Node Classifier. In short, if I manually add a test client into site.pp, it will retrieve the proper catalog / classes, but I would like to avoid having to do that. I''m also using environments (production/testing/ development) as well, but think I have most of

Hi, When I run puppet agent --test --environment 42A, I have the following warning : Warning: Local environment: "42A" doesn''t match server specified node environment "production", switching agent to "production". ... The puppet manifest for the environment "42A" isn''t applied. The puppet version is 3.3.1-1puppetlabs1 on agent and

Hello, Running into a problem when wanting to daemon-ize the agent. It doesnt seems to do anything: - cannot find any daemon process with (ps aux | grep puppet) - the config is not updated after editing some params on the master - /var/log/puppet stay empty... while, when logged as root, it is working without issue with $puppet agent --test. ##Conf Ubuntu 12.04 Puppet 2.7.11 ## Daemon is

I am trying to configure puppet with LDAP repository . I have set puppet schema and I have also added node definition at LDAP. Here is my configuration details . ############################################################## Puppet.conf node_terminus = ldap ldapserver = 10.250.11.127 ldapbase = ou=Hosts,dc=xyz,dc=com ldapassword = secret

All, For those that are using external nodes (as local files) and multiple environments, where do you put the external node files? Ie, do you put them down in the environment itself /etc/puppet/env/env1/manifests/extdata/nodes /etc/puppet/env/env.../manifests/extdata/nodes /etc/puppet/env/envN/manifests/extdata/nodes OR, up above the environments? /etc/puppet/manifests/extdata/nodes Which

All, I am sure this is just something I am doing wrong, but I am trying to implement a node classifier (shell script) to have my nodes inherit the proper classes. However, when I run it I am not getting any classes except those that are defined in default. Rather than going into detail showing all of my configurations right off the bat, I have a question: I just stood up a

Hello All, I''m trying to start using external nodes under foreman, and I''m running into some issues. I have the entries in puppet.conf: [main] external_nodes = /etc/puppet/external_node.rb node_terminus = exec The enternal_node.rb script is the one that came with foreman: #!/usr/bin/ruby # a simple script which fetches external nodes from Foreman # you

Hi, I''m trying to puppet kick with class option. Pupper Master: puppetmaster.example.com Puppet Client1: host1.example.net Puppet Client2: host2.example.net But I get this error. --- [root@puppetmaster ~]# puppet kick --class test --debug test: host1.example.net.example.com, host2.example.net.example.com Triggering host1.example.net.example.com, host2.example.net.example.com Host

Seems straight forward enough but I keep getting errors. On a client... err: Could not retrieve catalog from remote server: Error 400 on SERVER: Failed when searching for node ubuntu5.ttinet: LDAP Search failed on the puppet master... puppet.conf [master] # ENC (external node classificiations) node_terminus = ldap ldapnodes = true ldapclassattrs = puppetclass # LDAP ldapserver =

Hello Gang, I''m working on scaling my puppet solution, and I''m deploying multiple masters w/ passenger that are going sit behind a load balancer. If anyone is using these type of setup, would you share how you deal with the SSL certs? I''ve been following Bode''s Blog (http://bodepd.com/wordpress/?p=7), and it''s not working to good for me.

Hi all, I am using puppet with an ENC script. In this scripts YAML output the environment (generally "production") is set. For testing purposes I would like to start puppet runs from the cmdline of a managed host like: $ puppet agent --onetime --no-daemonize --verbose --no-splay --environment development The problem is the --environment Parameter is not being used if an environment

Hi- I recently upgrade from 0.24 to 0.25. In my 0.24 config, I had LDAP working such that Puppet was matching nodes in my directory to determine what classes to apply. I upgraded to 0.25 and this stopped working. I do not even see attempts from the Puppetmaster to search the directory (i.e., no connections to the ldap server). I *did* update the puppetmasterd conf, adding the variable

Hi guys, I have a box that needs to identify itself to the puppetmaster as something different from the FQDN. I added certname to the agent configuration before the first run, but it doesn''t seem to be sufficient. The certificate was generated for the FQDN, and the host appears in the dashboard as the FQDN, and the node name used to evaluate the manifest is also the FQDN. I would

I am trying to get a custom fact to sync. The fact is in a module. It will sync if I run puppet with "--pluginsync" but not otherwise. I have "pluginsync=true" in my puppet.conf. Shouldn''t the command line option and puppet.conf option have the same results? -- You received this message because you are subscribed to the Google Groups "Puppet Users" group.

I''m trying to use environments and seem to be failing. Right now I have 4 defined environments: production, cat, development, beta They are defined as follows on my puppetmaster: cat /etc/puppet/puppet.conf [main] pluginsync = true vardir = /var/lib/puppet manifest = /etc/puppet/environments/production/site.pp modulepath = /etc/puppet/environments/production/modules [master] reports =