similar to: ERB template, both client and master data

Hello list, I am having a problem with template file. Why are variables not interpolated? [root@puppet manifests]# cat /etc/motd memory free = <%= memoryfree %> domain = <%= domain %> operating system = <%= operatingsystem %> This is the template file [root@puppet manifests]# cat ../templates/motd.erb memory free = <%= memoryfree %> domain = <% domain %>

Hello Puppet list, I am taking over the puppet configuration of a sysadmin who left, and am having troubles deploying puppet to a new node. We are using puppet v2.7.3 both on the client and the puppetmaster, on Ubuntu 10.10. The node asks for a certificate fine, and I signed it on the puppetmaster. For the following logs extract I ve replaced the FQDN of my node by puppet.example.com. When doing

Hello I have been using puppet for a while now, more or less successfully on SLES 11 and CentOS 5.5 currently I am using puppet 2.6.6 I now am trying it out on redhat 6, and now i run into an problem with even the simplest of modules/classes The error I get is : debug: /Stage[main]/Motd/File[/etc/motd]/content: Executing ''diff -u / etc/motd

Hi, I want to introduce "Proxmox" as new value in $::operatingsystem. "Proxmox" is based on Debian, so the normal value is currently "Debian". To change that, I just write a custom fact based on the facter fact "operatingsystem" Facter.add(:operatingsystem) do > ... > setcode do > ... > elsif

Just upgraded to 2.7.6 and the yumrepo type does not write out our yum configs correctly, anyone experiencing this? Documentation hasn''t changed from what I can tell for this type. # facter -version 1.6.2 # puppetd --version 2.7.6 # facter architecture x86_64 # facter operatingsystem Fedora # facter operatingsystemrelease 14 ==== My manifest ==== yumrepo {

In the documentation, there is an example such as this: case $operatingsystem { sunos: { include solaris } # apply the solaris class redhat: { include redhat } # apply the redhat class default: { include generic } # apply the generic class } I''ve seen the $operatingsystem variable used elsewhere. What actually puts the value into the $operatingsystem variable? Does

I''ve run into an odd one on one of my new RHEL 6 boxes. Puppet and Facter seem to disagree about the value of a fact. Puppet version: 2.7.9 Facter version: 1.6.4 Module: puppetlabs-apache apache::params falls through its if structure: if $::osfamily == ''redhat'' or $::operatingsystem == ''amazon'' { ... } elsif $::osfamily ==

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

Trying to cleanup warning messages like the following: Dynamic lookup of $domain at /etc/puppetlabs/puppet/modules/centrifydc/templates/centrifydc.conf.erb:222 is deprecated. Support will be removed in Puppet 2.8. Use a fully-qualified variable name (e.g., $classname::variable) or parameterized classes. Do I simply replace <%= domain %> with <%= ::domain %> ? Same goes with

Hi. I have the following facts available: # facter | grep oper operatingsystem => CentOS operatingsystemrelease => 6.2 Now, if I wish to use conditionals on these facts, I have to do it like this: case $operatingsystem {} case $::operatingsystemrelease {} I''m puzzled as to why can''t I just use $operatingsystemrelease, and what do these two semicolons mean? Thank

Hello, I did make a stupid fault: not commiting changes to version control :-( After the installation of puppet-dashboard, I added a recipe to add report = true to puppet config files on clients. Now all Puppet clients don''t update because of an error... What can be the various reasons for an ''400'' error?? I guess it has something to do with rights. Jun 28 09:52:36 pm

Hey all. I am trying to set up puppet for the first time and I am having the following issues. On the client when I run it I get this error. Running puppet agent it should configure itself now /usr/local/lib/ruby/gems/1.9.1/gems/facter-1.6.3/lib/facter/util/config.rb:7: Use RbConfig instead of obsolete and deprecated Config. /usr/local/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in

Hi all, First off, we''re running Puppet 2.7.6 with Ruby 1.8.7 on CentOS 6.0. Now, I''m using tildes in a template to prevent newlines from appearing but ruby/puppet is choking on them. */tmp/puppet$ cat test.erb* Line 1: Line 2 will exist if running on CentOS. <% if operatingsystem == "CentOS" ~%> Line 2: Yay, we''re running CentOS. <% end ~%>

Hi all, I''ve finally gotten around to releasing Facter 1.5. As the version bump implies, this is a relatively significant release (for a 2.3k line program, anyway). Mostly, the biggest change is refactoring the code internally so that all of the functionality is split into separate classes in separate files. Also, the facts are all loaded on-demand, which provides dramatic

Hello, I have a file which varies depending on which OS/version it''s running. I tried to make a nested source parameter like this, but it didn''t work: source => $operatingsystem ? { Debian => "puppet://myserver.com/files/os/debian/etc/ssh/sshd_config", Gentoo => "puppet://myserver.com/files/os/gentoo/etc/ssh/sshd_config", RedHat =>

Hi I am new in Puppet and i have one error when i test Postgresql module in infrastructure mode. I''m using Puppet 3.1.0 in Debian squeeze or 6.0.7 i tape the next command puppetd -t -v and this is the error info: Retrieving plugin info: Loading facts in pe_version info: Loading facts in postgres_default_version info: Loading facts in iptables info: Loading facts in puppet_vardir

I''m running puppet 0.24.6 on CentOS 5.2 from a puppetmaster on a virtual server to a variety of client servers both virtual and metal running either CentOS 5.2 or Fedora Core 10. I want to extend this to servers running RHEL 5 (and 6) in the near future. My problem is I have puppet set up with all repositories (mirrored locally using cobbler) included in one file in

Hello, I have been perusing the documentation looking for the default list of variables that puppet defines such as $operatingsystem. For instance, how is $host translated; <host>.<domain>, or just <host> and where can I find this information. Thank you, -- Rob -- ____________________________________________________________________________________ Never miss an email

Is there a list somewhere? How do I know what $operatingsystem, for example, is going to be set to? Using ''solaris'' seems to work, but I haven''t tested ''ubuntu'' and ''redhat'' yet (haven''t gotten that far). It''d be nice to have a list of available vars, along with "how they are set." -Charlie

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