similar to: fqdn & templates

Hi Does anyone know if the following is supposed to work? ------------------------------------------------------ site.pp case $psi_rank { Devel: { import "Devel/psi_gfa/*" import "Devel/nodes" import "Devel/os/yum_update" } Prod: { import "Prod/psi_gfa/*" import "Prod/nodes" import

Hi All. I am using: #rpm -qa | egrep ''puppet|facter'' puppetlabs-release-6-7.noarch puppet-3.1.1-1.el6.noarch facter-1.7.1-1.el6.x86_64 on: #cat /etc/redhat-release ; uname -r CentOS release 6.4 (Final) 2.6.32-358.11.1.el6.centos.plus.x86_64 My hostname is server.one.two.com: # hostname server.one.two.com # hostname --fqdn one.two.com #grep HOSTNAME /etc/sysconfig/network

I testing Puppet 0.19.3. If we decide to use it, we''d deploy it across several thousand hosts. The method described for creating client certificates described in the documentation - running "puppetd --server <server> --waitforcert 60 --test" and "puppetca --sign <client>" - is not practical for our installation. I''ve tried creating

Sometimes "facter --yaml" doesn''t list all the values specified on the command line. I can''t find rhyme nor reason why. Here''s a demo to show what I mean: # facter --version 1.5.7 # facter --yaml fqdn macaddress lsbdistcodename --- fqdn: my.host.name.example.com lsbdistcodename: squeeze macaddress: "00:00:00:00:00:00" We had been using the above

Hi everyone, Here are the manifest I am using: In file ''*modules/test/manifest/init.pp*'': class test ( $test = undef, ) { notice("Here is the message: ${test}") } Now in ''*modules/saas/manifests/client/sudo.pp*'': class saas::client::sudo { class { ''test'': } } Now in ''*manifests/sites.pp*'': import

I could swear this worked fine earlier.. Now facter, and hence puppet, do not see the domain name anymore: What could cause this? C:\Temp>facter --version 1.6.2 C:\Temp>facter | findstr kernel kernel => windows kernelmajversion => 6.1 kernelrelease => 6.1.7601 kernelversion => 6.1.7601 C:\Temp>facter fqdn NCS-VDI-05.none C:\Temp>facter hostname NCS-VDI-05

Im new to puppet and installed it in my home lab to mess with, when i installed it i used the hostname rather than FQDN so went back and changed puppet and reran the certificate tool to regenerate the certificates etc, the agent works fine now but i am getting an mccollective error i think, is there anything in the config i need to change for mccollective after altering the name to the FQDN?

Hello! I''ve been trying to use facts from Facter in a custom function. I''ve been following Matthew''s entry in the wiki (http://www.reductivelabs.com/trac/puppet/wiki/WritingYourOwnFunctions). What i''m seeing is that Facter[''fqdn''].value is always returning the fqdn of the puppetmaster host. I was expecting the fqdn of the client host.

I''ve got a single puppet master (2.7.19 + facter 1.6.11) controlling a number of nodes (2.7.17 + facter 1.6.8-10). On all of thse, fact absed variables work as expected (such as $::operatingsystem and $::fqdn). However, on my puppet master, when I run ''puppet agent --test'' all fact based variables are combing back as empty strings. For example. I have a line in a

Not sure if this is another issue cropping up with 0.24.1 but I''m getting the following: info: Loading fact raid /etc/puppet/facts/location.rb:5: private method `split'' called for nil:NilClass (NoMethodError) from /usr/lib/ruby/site_ruby/1.8/facter.rb:510:in `call'' from /usr/lib/ruby/site_ruby/1.8/facter.rb:510:in `value'' from

I recently upgraded my Puppetmaster to 0.24.4 and it looks like my templates are not working properly. All of my clients use the same certificate, built by my original client "xx". I do this using the certname=blah parameter in the puppet.conf on each client. Up until I upgraded each client would use the "xx" certificate (which I had renamed to "blah") and

I have this in nodes.pp $puppetmaster_fqdn = generate("/usr/bin/facter","fqdn") and this in a template http://<%= puppetmaster_fqdn %>:8080 When puppet runs, this is the result: http://puppet.home :8080 Anybody any clue to whats causing this? I''ve tried -%> -- You received this message because you are subscribed to the Google Groups "Puppet

One one of my new vmware guests... puppetd -v spits out a bunch of err & warnings about "State group failed"... what does this mean? <snip> info: Caching configuration at /var/lib/puppet/localconfig.yaml err: Could not create root: Could not find a default provider for group warning: file=/etc/yum.repos.d/: State group failed: Could not find a default provider for group

I''m having a heck of a time trying to fix #1178, which is a problem related to inconsistent node names, and it all stems from the ''node_name'' setting. In the default setup, your certificate gets created with your host''s fully qualified node name, and Puppet uses the value from the certificate for everything. In addition, there''s a setting,

I have 2 RHEL 5.4 systems where all facter lsb* items are missing. Any ideas? Sanitized facter output: architecture => i386 domain => missyou.edu facterversion => 1.5.7 fqdn => broken.missyou.edu hardwareisa => i686 hardwaremodel => i686 hostname => broken id => root interfaces => eth0,sit0 ipaddress => 1.2.1.5 ipaddress_eth0 => 1.2.1.5 is_virtual => true

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 need to get an array of hostnames of clients of the puppet server. There doesn''t seem to be a simple way to do this so I''ve tried a few methods. I''ve tried a curl expression in a fact like this: curl -s -k -H "Accept: yaml" https://localhost:8140/production/facts_search/search?facts.nodetypet=testnodes where I''ve got a nodetype fact which works

Hi, First of all, this is my very first message to this list, so please bear with me while I''m getting used to it. Sorry for any non-standard way to ask a question here which I can be using without prior knowledgment. I would like to be able to set up some config parameters on a given node which is going to be config-managed by Puppet and, for various reasons, I would like to be able

Hi, I''m new to Puppet, but it looks very good, so far. We are going to use it for a multi-tier (DEV, QA, staging, production) environment which is consists of web, app, and database servers. I have a couple of suggestions for the Puppet documentation that may save others some time. First, it seems node names MUST be FQDNs (hostname and hostname. will not work). Since we are not using

hi, i''m trying to set up my puppetmaster infrastructure with multiple puppetservers behind load balancers in each of our datacenters. i''m using 0.24.6. i''ve read the howto on puppet scalability, and i think i''ve got the ssl config working correct, but i''m noticing that when puppetd is used to build a puppetmaster, some of the files in $vardir/ ssl